All of lore.kernel.org
 help / color / mirror / Atom feed
* qemu librbd patches
@ 2011-05-09  8:59 Christian Brunner
  2011-05-09 15:22 ` Josh Durgin
  2011-05-24 20:10 ` Josh Durgin
  0 siblings, 2 replies; 5+ messages in thread
From: Christian Brunner @ 2011-05-09  8:59 UTC (permalink / raw)
  To: ceph-devel

Hi,

after upgrading to qemu with josh's librbd patches I'm triggering the
following assertion, when I'm running "yum upgrade" inside a guest.

I suspect there is a race condition somewhere, but I don't have a clue
at the moment.

Regards,
Christian

common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
common/Mutex.h: 118: FAILED assert(r == 0)
common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
common/Mutex.h: 118: FAILED assert(r == 0)
 ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
 1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
 2: /usr/bin/qemu-kvm() [0x46a165]
 3: /usr/bin/qemu-kvm() [0x46a1d0]
 4: /usr/bin/qemu-kvm() [0x44349f]
 ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
 1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
 2: /usr/bin/qemu-kvm() [0x46a165]
 3: /usr/bin/qemu-kvm() [0x46a1d0]
 4: /usr/bin/qemu-kvm() [0x44349f]
 ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
 1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
 2: /usr/bin/qemu-kvm() [0x46a165]
 3: /usr/bin/qemu-kvm() [0x46a1d0]
 4: /usr/bin/qemu-kvm() [0x44349f]
 ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
 1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
 2: /usr/bin/qemu-kvm() [0x46a165]
 3: /usr/bin/qemu-kvm() [0x46a1d0]
 4: /usr/bin/qemu-kvm() [0x44349f]
terminate called after throwing an instance of 'ceph::FailedAssertion'
--
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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: qemu librbd patches
  2011-05-09  8:59 qemu librbd patches Christian Brunner
@ 2011-05-09 15:22 ` Josh Durgin
  2011-05-10  8:29   ` Yehuda Sadeh Weinraub
  2011-05-24 20:10 ` Josh Durgin
  1 sibling, 1 reply; 5+ messages in thread
From: Josh Durgin @ 2011-05-09 15:22 UTC (permalink / raw)
  To: chb; +Cc: ceph-devel

On Mon, 9 May 2011 10:59:41 +0200, Christian Brunner <chb@muc.de>
wrote:
> Hi,
> 
> after upgrading to qemu with josh's librbd patches I'm triggering the
> following assertion, when I'm running "yum upgrade" inside a guest.
> 
> I suspect there is a race condition somewhere, but I don't have a clue
> at the moment.

This is similar to a race condition Stefan encountered
(http://marc.info/?l=kvm&m=130225223223016&w=2),
although this crash was during a write whereas his test was just
reading the image.

> 
> Regards,
> Christian
> 
> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread
> '0x7fea16b36700'
> common/Mutex.h: 118: FAILED assert(r == 0)

Usually this assert fails due to a use-after-free. If you've got
a core file, could you print the lock that hit this assert and
the data structure containing it?

Thanks!
Josh

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: qemu librbd patches
  2011-05-09 15:22 ` Josh Durgin
@ 2011-05-10  8:29   ` Yehuda Sadeh Weinraub
  0 siblings, 0 replies; 5+ messages in thread
From: Yehuda Sadeh Weinraub @ 2011-05-10  8:29 UTC (permalink / raw)
  To: Josh Durgin; +Cc: chb, ceph-devel

On Mon, May 9, 2011 at 8:22 AM, Josh Durgin <josh.durgin@dreamhost.com> wrote:
> On Mon, 9 May 2011 10:59:41 +0200, Christian Brunner <chb@muc.de>
> wrote:
>> Hi,
>>
>> after upgrading to qemu with josh's librbd patches I'm triggering the
>> following assertion, when I'm running "yum upgrade" inside a guest.
>>
>> I suspect there is a race condition somewhere, but I don't have a clue
>> at the moment.
>
> This is similar to a race condition Stefan encountered
> (http://marc.info/?l=kvm&m=130225223223016&w=2),
> although this crash was during a write whereas his test was just
> reading the image.
>
>>
>> Regards,
>> Christian
>>
>> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread
>> '0x7fea16b36700'
>> common/Mutex.h: 118: FAILED assert(r == 0)
>
> Usually this assert fails due to a use-after-free. If you've got
> a core file, could you print the lock that hit this assert and
> the data structure containing it?

Btw, probably not related but should be pointed out. There are a few
places in librbd where it fails to take the image context lock, and
it's probably racy. It's probably a big problem when resizing image,
but there might be other issues.

Yehuda

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: qemu librbd patches
  2011-05-09  8:59 qemu librbd patches Christian Brunner
  2011-05-09 15:22 ` Josh Durgin
@ 2011-05-24 20:10 ` Josh Durgin
  2011-05-25 19:09   ` Christian Brunner
  1 sibling, 1 reply; 5+ messages in thread
From: Josh Durgin @ 2011-05-24 20:10 UTC (permalink / raw)
  To: chb; +Cc: ceph-devel

On 05/09/2011 01:59 AM, Christian Brunner wrote:
> Hi,
>
> after upgrading to qemu with josh's librbd patches I'm triggering the
> following assertion, when I'm running "yum upgrade" inside a guest.
>
> I suspect there is a race condition somewhere, but I don't have a clue
> at the moment.
>
> Regards,
> Christian
>
> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
> common/Mutex.h: 118: FAILED assert(r == 0)
> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread '0x7fea16b36700'
> common/Mutex.h: 118: FAILED assert(r == 0)
>   ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>   1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>   2: /usr/bin/qemu-kvm() [0x46a165]
>   3: /usr/bin/qemu-kvm() [0x46a1d0]
>   4: /usr/bin/qemu-kvm() [0x44349f]
>   ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>   1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>   2: /usr/bin/qemu-kvm() [0x46a165]
>   3: /usr/bin/qemu-kvm() [0x46a1d0]
>   4: /usr/bin/qemu-kvm() [0x44349f]
>   ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>   1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>   2: /usr/bin/qemu-kvm() [0x46a165]
>   3: /usr/bin/qemu-kvm() [0x46a1d0]
>   4: /usr/bin/qemu-kvm() [0x44349f]
>   ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>   1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>   2: /usr/bin/qemu-kvm() [0x46a165]
>   3: /usr/bin/qemu-kvm() [0x46a1d0]
>   4: /usr/bin/qemu-kvm() [0x44349f]
> terminate called after throwing an instance of 'ceph::FailedAssertion'

Hi Christian,

Could you try to get a core file for this? I still haven't been able to 
reproduce it.

Thanks,
Josh

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: qemu librbd patches
  2011-05-24 20:10 ` Josh Durgin
@ 2011-05-25 19:09   ` Christian Brunner
  0 siblings, 0 replies; 5+ messages in thread
From: Christian Brunner @ 2011-05-25 19:09 UTC (permalink / raw)
  To: ceph-devel

I'm sorry. At the moment I don't have a core file available and my
colleagues don't allow me to reproduce it. ;-)

We should get a new server in one or two weeks. I will try to get a core then.

Christian

2011/5/24 Josh Durgin <josh.durgin@dreamhost.com>:
> On 05/09/2011 01:59 AM, Christian Brunner wrote:
>>
>> Hi,
>>
>> after upgrading to qemu with josh's librbd patches I'm triggering the
>> following assertion, when I'm running "yum upgrade" inside a guest.
>>
>> I suspect there is a race condition somewhere, but I don't have a clue
>> at the moment.
>>
>> Regards,
>> Christian
>>
>> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread
>> '0x7fea16b36700'
>> common/Mutex.h: 118: FAILED assert(r == 0)
>> common/Mutex.h: In function 'void Mutex::Lock(bool)', in thread
>> '0x7fea16b36700'
>> common/Mutex.h: 118: FAILED assert(r == 0)
>>  ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>>  1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
>> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>>  2: /usr/bin/qemu-kvm() [0x46a165]
>>  3: /usr/bin/qemu-kvm() [0x46a1d0]
>>  4: /usr/bin/qemu-kvm() [0x44349f]
>>  ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>>  1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
>> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>>  2: /usr/bin/qemu-kvm() [0x46a165]
>>  3: /usr/bin/qemu-kvm() [0x46a1d0]
>>  4: /usr/bin/qemu-kvm() [0x44349f]
>>  ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>>  1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
>> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>>  2: /usr/bin/qemu-kvm() [0x46a165]
>>  3: /usr/bin/qemu-kvm() [0x46a1d0]
>>  4: /usr/bin/qemu-kvm() [0x44349f]
>>  ceph version 0.27.1 (commit:44900d4c13f02913b3347cac3e1dc33632d5b8ff)
>>  1: (librbd::aio_write(librbd::ImageCtx*, unsigned long, unsigned
>> long, char const*, librbd::AioCompletion*)+0x54e) [0x7fea2299523e]
>>  2: /usr/bin/qemu-kvm() [0x46a165]
>>  3: /usr/bin/qemu-kvm() [0x46a1d0]
>>  4: /usr/bin/qemu-kvm() [0x44349f]
>> terminate called after throwing an instance of 'ceph::FailedAssertion'
>
> Hi Christian,
>
> Could you try to get a core file for this? I still haven't been able to
> reproduce it.
>
> Thanks,
> Josh
> --
> 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
>
--
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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-05-25 19:09 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-09  8:59 qemu librbd patches Christian Brunner
2011-05-09 15:22 ` Josh Durgin
2011-05-10  8:29   ` Yehuda Sadeh Weinraub
2011-05-24 20:10 ` Josh Durgin
2011-05-25 19:09   ` Christian Brunner

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.