diff --git a/ChangeLog b/ChangeLog
index 3b1c493..07e8940 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1 +1,172273 @@
-ChangeLog is maintained by "git log".
+commit 754e2658ba58743bc4ef2d843410334e639a96e1
+Author: Niels de Vos <ndevos@redhat.com>
+Date:   Fri Jul 8 16:17:24 2016 +0200
+
+    doc: add release-notes for 3.8.1
+    
+    BUG: 1345943
+    Change-Id: I65e17b1baaff7b2e81ab46de95389d1c80a7f52e
+    Signed-off-by: Niels de Vos <ndevos@redhat.com>
+
+commit f4044fa4ff75389de0cf17008179d55ac0a15b33
+Author: Atin Mukherjee <amukherj@redhat.com>
+Date:   Mon May 9 12:14:37 2016 +0530
+
+    glusterd: search port from last_alloc to base_port
+    
+    Backport of http://review.gluster.org/14268
+    
+    If a brick process is killed ungracefully then GlusterD wouldn't receive a
+    PMAP_SIGNOUT event and hence the stale port details wouldn't be removed out.
+    
+    Now consider the following case:
+    1. Create a volume with 1 birck
+    2. Start the volume (say brick port allocated is 49152)
+    3. Kill the brick process by 'kill -9'
+    4. Stop & delete the volume
+    5. Recreate the volume and start it. (Now the brick port gets 49153)
+    6. Mount the volume
+    
+    Now in step 6 mount will fail as GlusterD will provide back the stale port
+    number given the query starts searching from the base_port.
+    
+    Solution:
+    
+    To avoid this, searching for port from last_alloc and coming down to base_port
+    should solve the issue.
+    
+    >Change-Id: I9afafd722a7fda0caac4cc892605f4e7c0e48e73
+    >BUG: 1334270
+    >Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
+    >Reviewed-on: http://review.gluster.org/14268
+    >Smoke: Gluster Build System <jenkins@build.gluster.org>
+    >NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
+    >CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

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