===== git log ====
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

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