===== git log ====
commit 05efb3cafdc2bd034d0a238342841e15e9197e13
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Jul 17 02:34:47 2019 +0530

    doc: Added release notes for 4.1.10
    
    Fixes: bz#1730489
    
    Change-Id: I333f73f13eb71ff65d4e1ea8d6d67972260d62e0
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit cf00b5711f00f7f8da041a9a1b8c5ce77c24c706
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.
    
    This is backport of below mainline fix:
     https://review.gluster.org/22839
    
    Change-Id: I9fa8f841e71d3c37d3819fbd430382928c07176c
    fixes: bz#1729223
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 54a5c58f6595ff5342df5b7c4c16a26db2fa02da
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.
    
    This is backport of below mainline fix -
     https://review.gluster.org/22840

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