Description of problem: This bug is to back-port the changes required to fix mem leaks related to fuse: fix inode and dentry leaks, originally reported in http://review.gluster.org/#/c/13324/ Version-Release number of selected component (if applicable): 3.6.9 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14403 (a) backport of fuse: fix inode and dentry leaks http://review.gluster.org/#/c/13324/) posted (#1) for review on release-3.6 by Vangelis Polakis
Hi, For this review request the smoke tests failed, as in all the latest requests for release 3.6 (http://review.gluster.org/#/q/project:glusterfs+branch:release-3.6) are you aware if there is a common issue for the failures in this release? Thank you, Olia
No, the smoke test failure is not a common issue for this release. You can see the build log at http://build.gluster.org/job/netbsd6-smoke/13840/console. There's a compile error.
Hi, thx, there are 3 reviews with similar errors. Also there is a relevant discussion in devel list ---------- Forwarded message ---------- From: Atin Mukherjee <atin.mukherjee83> Date: Fri, May 20, 2016 at 7:10 PM Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6 To: Emmanuel Dreyfus <manu> Cc: Gluster Devel <gluster-devel> No, we didn't solve this problem yet. Niels had a patch up for review to fix it but unfortunately it didn't. Kaushal also tried to reproduce it on a netbsd machine, but nothing failed for him. -Atin Sent from one plus one On 20-May-2016 9:25 PM, "Emmanuel Dreyfus" <manu> wrote: > > On Fri, May 20, 2016 at 05:43:07PM +0300, Angelos SAKELLAROPOULOS wrote: > > May I ask why following review requests are not submitted to release-3.6 ? > > It seems that they fail in netbsd, freebsd smoke tests which are not > > related to code changes. > > There are build errors. I am note sur how you could have inherited > them from git checkout, since previous changes were supposed to > pass smoke too. If you are sure the error are not yours, you > can try to rebase. > How should we proceed ?
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.'