All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: sjust@redhat.com
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: dumpling integration : valgrind leak
Date: Fri, 30 Jan 2015 18:56:28 +0100	[thread overview]
Message-ID: <54CBC5CC.5050706@dachary.org> (raw)
In-Reply-To: <CA+4uBUZR3Dvy5gszM2pOVuLsjDGAKdhRo8YLnzaWg-HOEWgcbw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2628 bytes --]

After a little digging I found https://github.com/ceph/ceph/commit/02fae9fc54c10b5a932102bac43f32199d4cb612 which seems to be a plausible fix in dumpling also https://github.com/ceph/ceph/pull/3552. What do you think ?

On 30/01/2015 16:35, Samuel Just wrote:
> Yeah, that's probably new.
> -Sam
> 
> On Fri, Jan 30, 2015 at 7:00 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Sam,
>>
>> I stumbled upon what seems to be a leak at http://pulpito.ceph.com/loic-2015-01-29_15:41:06-rados-dumpling-backports---basic-multi/730305/ and the valgrind xml file is at http://tracker.ceph.com/attachments/download/1610/v.txt
>>
>>     <text>612 (584 direct, 28 indirect) bytes in 1 blocks are definitely lost in loss record 268 of 287</text>
>>       <fn>operator new(unsigned long)</fn>
>>       <fn>ReplicatedPG::get_object_context(hobject_t const&amp;, bool)</fn>
>>       <line>4585</line>
>>       <fn>ReplicatedPG::find_object_context(hobject_t const&amp;, ObjectContext**, bool, snapid_t*)</fn>
>>       <line>4658</line>
>>       <fn>ReplicatedPG::do_op(std::tr1::shared_ptr&lt;OpRequest&gt;)</fn>
>>       <line>835</line>
>>       <fn>PG::do_request(std::tr1::shared_ptr&lt;OpRequest&gt;, ThreadPool::TPHandle&amp;)</fn>
>>       <line>1455</line>
>>       <fn>OSD::dequeue_op(boost::intrusive_ptr&lt;PG&gt;, std::tr1::shared_ptr&lt;OpRequest&gt;, ThreadPool::TPHandle&amp;)</fn>
>>       <line>7169</line>
>>       <fn>OSD::OpWQ::_process(boost::intrusive_ptr&lt;PG&gt;, ThreadPool::TPHandle&amp;)</fn>
>>       <line>7141</line>
>>       <fn>ThreadPool::WorkQueueVal&lt;std::pair&lt;boost::intrusive_ptr&lt;PG&gt;, std::tr1::shared_ptr&lt;OpRequest&gt; &gt;, boost::intrusive_ptr&lt;PG&gt; &gt;::_void_process(void*, ThreadPool::TPHandle&amp;)</fn>
>>       <line>191</line>
>>       <fn>ThreadPool::worker(ThreadPool::WorkThread*)</fn>
>>       <line>128</line>
>>       <fn>ThreadPool::WorkThread::entry()</fn>
>>       <line>318</line>
>>       <fn>start_thread</fn>
>>       <line>312</line>
>>       <fn>clone</fn>
>>       <line>111</line>
>>
>> A quick grep of get_object_context in redmine does not hit. Does it ring a bell ?
>>
>> Cheers
>>
>> dumpling backport inventory: http://tracker.ceph.com/issues/10560
>> ticket: http://tracker.ceph.com/issues/10697
>>
>> --
>> 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
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2015-01-30 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 15:00 dumpling integration : valgrind leak Loic Dachary
2015-01-30 15:35 ` Samuel Just
2015-01-30 17:56   ` Loic Dachary [this message]

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=54CBC5CC.5050706@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sjust@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.