Open mohit84 opened 3 months ago
The brick process is getting crashed due to stack overflow while unref namespace inode, the ns inode was introduced by the patch ((https://github.com/gluster/glusterfs/pull/1763)
Solution: __inode_destroy is calling inode_unref that is again calling inode_unref become a recursive call and eventually a brick process is getting crashed. To avoid a crash for namespace inode call only __inode_ref.
Fixes: #4295 Change-Id: If5deb06b726a5e7dfedd2784bddcef81e6e5d7d9 Signed-off-by: Mohit Agrawal moagrawa@redhat.com (Cherry picked from commit 80ecbbac0cfb4d45684d132f78a41fcaaafeb2ea) (Reviewed on upstream link https://github.com/gluster/glusterfs/pull/4302)
Fixes: #4295 Change-Id: If5deb06b726a5e7dfedd2784bddcef81e6e5d7d9
/run regression
The brick process is getting crashed due to stack overflow while unref namespace inode, the ns inode was introduced by the patch ((https://github.com/gluster/glusterfs/pull/1763)
Solution: __inode_destroy is calling inode_unref that is again calling inode_unref become a recursive call and eventually a brick process is getting crashed. To avoid a crash for namespace inode call only __inode_ref.
Fixes: #4295 Change-Id: If5deb06b726a5e7dfedd2784bddcef81e6e5d7d9