===== git log ====
commit 6028ef61d2f4078d3256a43b0efe3d2bd1a3c649
Author: Tamar Shacked <tshacked@redhat.com>
Date:   Sun May 9 13:20:14 2021 +0300

    doc: Added release 8.5 notes (#2420)
    
    * doc: Added release 8.5 notes
    
    Updates: #2340
    
    Change-Id: I890bc71a012073e119b0cef6ae07fc8a1c89ca0b
    Signed-off-by: Tamar Shacked <tshacked@redhat.com>

commit 065a24e0a09ca44d18977a6668cfb3812c510d24
Author: mohit84 <moagrawa@redhat.com>
Date:   Sat May 8 07:02:33 2021 +0530

    core: Avoid several dict OR key is NULL message in brick logs (#1910) (#2345)
    
    Problem: dict_get_with_ref throw a message "dict or key is NULL"
             if dict or key is NULL.
    
    Solution: Before access a key check if dictionary is valid.
    
    > Fixes: #1909
    > Change-Id: I50911679142b52f854baf20c187962a2a3698f2d
    > Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    > (Cherry picked from commit de1b26d68e31b029a59e59a47b51a7e3e6fbfe22)
    > (Reviewed on upstream link https://github.com/gluster/glusterfs/pull/1910)
    
    Fixes: #1909
    Change-Id: I50911679142b52f854baf20c187962a2a3698f2d
    Signed-off-by: Mohit Agrawal moagrawa@redhat.com

commit 7f51663720b3aaa2251ed90e0fec1c77edd3d677
Author: Pranith Kumar Karampuri <pranith.karampuri@phonepe.com>
Date:   Sat May 8 05:11:39 2021 +0530

    protocol/client: Fix lock memory leak (#2338) (#2356)
    
    Problem-1:
    When an overlapping lock is issued the merged lock is not assigned the
    owner. When flush is issued on the fd, this particular lock is not freed
    leading to memory leak
    
    Fix-1:
    Assign the owner while merging the locks.
    
    Problem-2:

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