===== git log ====
commit ee067308c35bf0c0c7509be4931182926617d2f2
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Jan 19 19:11:26 2018 -0500

    doc: Added release notes for 3.13.2
    
    Change-Id: I80f411f3820f82cb27fd5f8cf1cf99d5565d8b9d
    BUG: 1530334
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 594345737f0a49cd6a17a724102d587f82b4cbb9
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jan 17 18:03:11 2018 +0530

    selinux-xlator : validate dict before calling dict_rename_key()
    
    Upstream reference :
    >Change-Id: I71da3b64e5e8c82e8842e119b2b05da3e2ace550
    >BUG: 1535772
    >Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    >(cherry picked from commit bee06ccd7b80e3f5804f0c7c7c56936fed6d2b4e)
    
    Change-Id: I71da3b64e5e8c82e8842e119b2b05da3e2ace550
    BUG: 1536294

commit b9e3b7f2753a5c8d56c1ed627a22dca3f2c3dd89
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Jan 17 17:30:06 2018 +0530

    cluster/afr: Adding option to take full file lock
    
    Problem:
    In replica 3 volumes there is a possibilities of ending up in split
    brain scenario, when multiple clients writing data on the same file
    at non overlapping regions in parallel.
    
    Scenario:
    - Initially all the copies are good and all the clients gets the value
      of data readables as all good.
    - Client C0 performs write W1 which fails on brick B0 and succeeds on
      other two bricks.
    - C1 performs write W2 which fails on B1 and succeeds on other two bricks.
    - C2 performs write W3 which fails on B2 and succeeds on other two bricks.
    - All the 3 writes above happen in parallel and fall on different ranges
      so afr takes granular locks and all the writes are performed in parallel.
      Since each client had data-readables as good, it does not see
      file going into split-brain in the in_flight_split_brain check, hence
      performs the post-op marking the pending xattrs. Now all the bricks
      are being blamed by each other, ending up in split-brain.

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