===== git log ====
commit bac5d7d60d14a190217fcd84fd0803a4d6a2e37d
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#1755678
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e3942babf00fe74dd3c3fc8502482967fbdb9ca5
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
    
    This is backport of below mainline patch -
    - https://review.gluster.org/#/c/glusterfs/+/23448/
    - bz#1753569
    
    release-6:
    - https://review.gluster.org/#/c/glusterfs/+/23491/
    
    Change-Id: Ibf513fcfcdad175f4d7eb6fa7a61b8feec6d33b5
    fixes: bz#1756002
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 6b3fec37931cbf3f7995b119e5a14702d5226772
Author: Sunny Kumar <sunkumar@redhat.com>

More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v7.0rc3
