From: Loic Dachary <loic@dachary.org>
To: John Spray <jspray@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: ceph-mds jewel backports leak
Date: Wed, 6 Jul 2016 12:51:32 +0200 [thread overview]
Message-ID: <577CE2B4.6010505@dachary.org> (raw)
Hi John,
While testing the CephFS jewel backports found in the jewel-backports branch, we ran into a memory leak that consistently happen:
http://pulpito.ceph.com/loic-2016-06-16_02:28:14-fs-jewel-backports---basic-smithi/263842
and that is not present in the jewel branch
http://pulpito.ceph.com/loic-2016-06-28_23:43:39-fs-jewel---basic-smithi/282493/
Meaning one of the backports is doing something wrong. Or there is a backport fixing the leak that is missing.
This one looks interesting to me
https://github.com/ceph/ceph/commit/37b7b09ee19ad64362c2faf63461353c03a36ada
There also are related to leaks but I'm not so sure.
https://github.com/ceph/ceph/commit/89f74c98ea43df46291c8bec890b3a75c7ce38b4
https://github.com/ceph/ceph/commit/4c52bf9ed47d52510536ebc34bd6c56adba1df53
If you have ideas on how to approach this and save random exploration time, it would be most welcome. If not, I'll get it eventually, no worries :-)
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-07-06 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:51 Loic Dachary [this message]
2016-07-06 11:53 ` ceph-mds jewel backports leak Loic Dachary
2016-07-07 10:54 ` John Spray
2016-07-07 11:52 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577CE2B4.6010505@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=jspray@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox