Re: Assertion error in librados

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxx> 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@xxxxxxxxxxx> 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@xxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux