===== git log ====
commit dc8583529731636d80fe7285c3cc6444d6aac67e
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Jan 16 15:27:03 2019 -0500

    doc: Release notes for 5.3
    
    Fixes: bz#1659085
    Change-Id: I5195e4eca6518e3122ea188e2f4891f5e68ca01a
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 561624aad540c4a7df49ab62bd8a9a75810d76b2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jan 11 15:00:27 2019 +0530

    fuse: add --lru-limit option
    
    The inode LRU mechanism is moot in fuse xlator (ie. there is no
    limit for the LRU list), as fuse inodes are referenced from
    kernel context, and thus they can only be dropped on request of
    the kernel. This might results in a high number of passive
    inodes which are useless for the glusterfs client, causing a
    significant memory overhead.
    
    This change tries to remedy this by extending the LRU semantics
    and allowing to set a finite limit on the fuse inode LRU.
    
    A brief history of problem:
    
    When gluster's inode table was designed, fuse didn't have any
    'invalidate' method, which means, userspace application could
    never ask kernel to send a 'forget()' fop, instead had to wait
    for kernel to send it based on kernel's parameters. Inode table
    remembers the number of times kernel has cached the inode based
    on the 'nlookup' parameter. And 'nlookup' field is not used by
    no other entry points (like server-protocol, gfapi etc).
    
    Hence the inode_table of fuse module always has to have lru-limit
    as '0', which means no limit. GlusterFS always had to keep all
    inodes in memory as kernel would have had a reference to it.
    Again, the reason for this is, kernel's glusterfs inode reference
    was pointer of 'inode_t' structure in glusterfs. As it is a
    pointer, we could never free it (to prevent segfault, or memory
    corruption).
    
    Solution:
    
    In the inode table, handle the prune case of inodes with 'nlookup'
    differently, and call a 'invalidator' method, which in this case is
    fuse_invalidate(), and it sends the request to kernel for getting

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