===== git log ====
commit d1c74321570e3ec77c1d91293549900f4605d613
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Tue Sep 20 13:04:56 2022 +0530

    Add GlusterFS 10.3 release notes (#3821)
    
    Updates: #3820
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 58cd388770d9c027b801b5acafcc421d57e1bfcf
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Tue Sep 20 12:39:22 2022 +0530

    posix_disk_space_check, dht_disk_usage: save multiplcation if using percentage (#3040) (#3818)
    
    If we are using percentage of free space, there's no need to multiply
    both the free space and the and the total size by buf.f_bsize,
    as we compare one to each other.
    
    Similar work in DHT's code.
    
    Also, switched from using a char ('p') to signify we are using percentage
    for disk usage to a simple boolean. True means we are using percentage.
    
    >Updates: #1000
    >Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Signed-off-by: Shwetha K Acharya
    
    Signed-off-by: Shwetha K Acharya
    Co-authored-by: Yaniv Kaul <ykaul@redhat.com>

commit 8ca6f5c72aaffb09e207c4eb8117f33872c9d657
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Mon Sep 19 11:42:10 2022 +0530

    lock/clear: Perform stack unwind outside of the inode lock (#3775) (#3808)
    
    While we handle lock interrupt xatrrs, the blocked locks
    are unwind with EINTR inside pl_inode lock. This is not
    a good idea, since the stack unwind may choose to wind
    a fop, and there can be deadlock if the wind fop requested
    for the pl_inode lock. One such example would be a EINTR
    call on a blocked lock with an fd having only one ref.
    This will result in calling pl_release while holding
    a lock on pl_inode. Since there is an pl_inode lock
    request inside a pl_release too, it will end up in a
    dead lock.
    

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