From: Gregory Farnum <greg@inktank.com>
To: Filippos Giannakos <philipgian@grnet.gr>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Josh Durgin <josh.durgin@inktank.com>,
Noah Watkins <noah.watkins@inktank.com>,
synnefo-devel@googlegroups.com
Subject: Re: Assertion error in librados
Date: Mon, 31 Mar 2014 10:10:08 -0700 [thread overview]
Message-ID: <CAPYLRzg3Qfpt+QS40iREznhCHgVEv=MAWaGNHZREr65AD9SRgQ@mail.gmail.com> (raw)
In-Reply-To: <20140328095443.GZ28819@philipgian-mac>
Nope, I don't think anybody's looked into it. If you have core dumps
you could get a backtrace and the return value referenced.
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
On Fri, Mar 28, 2014 at 2:54 AM, Filippos Giannakos <philipgian@grnet.gr> wrote:
> Hello,
>
> We recently bumped again into the same assertion error.
> Do you have any indications or update regarding the cause ?
>
> On Tue, Feb 25, 2014 at 11:26:15AM -0800, Noah Watkins wrote:
>> On Tue, Feb 25, 2014 at 9:51 AM, Josh Durgin <josh.durgin@inktank.com> wrote:
>> > That's a good idea. This particular assert in a Mutex is almost always
>> > a use-after-free of the Mutex or structure containing it though.
>>
>> I think that a use-after-free will also throw an EINVAL (assuming it
>> isn't a pathalogical case) as pthread_mutex_lock checks an
>> initialization magic variable. I think that particular mutex isn't
>> initialized with flags that would cause any of the other possible
>> return values.
>
> Kind regards,
> --
> Filippos
> <philipgian@grnet.gr>
next prev parent reply other threads:[~2014-03-31 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 14:49 Assertion error in librados Filippos Giannakos
2014-02-25 15:28 ` Gregory Farnum
2014-02-25 15:41 ` Yehuda Sadeh
2014-02-25 15:58 ` Filippos Giannakos
2014-02-25 17:33 ` Noah Watkins
2014-02-25 17:51 ` Josh Durgin
2014-02-25 19:26 ` Noah Watkins
2014-03-28 9:54 ` Filippos Giannakos
2014-03-31 17:10 ` Gregory Farnum [this message]
2014-02-25 17:51 ` Gregory Farnum
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='CAPYLRzg3Qfpt+QS40iREznhCHgVEv=MAWaGNHZREr65AD9SRgQ@mail.gmail.com' \
--to=greg@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=noah.watkins@inktank.com \
--cc=philipgian@grnet.gr \
--cc=synnefo-devel@googlegroups.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.