===== git log ====
commit bef7c8e54e89413ee419fcc369adaf74399c39b8
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Sun May 17 12:05:49 2020 +0000

    doc: Added release 7.6 notes
    
    Fixes: #1247
    
    Change-Id: Ic9571066aa83fc2142e3583ddf1f1b885e83470c
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit b53ba17dbfd2d18c10e2c308b8899d36726ab440
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

commit 4d3a249418ef6b391c93943ff29f58145448cf7b
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

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