All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: reproductible kernel oops with kernel 3.2 inside kvm
Date: Thu, 17 May 2012 15:21:55 -0700	[thread overview]
Message-ID: <4FB57A03.70309@inktank.com> (raw)
In-Reply-To: <4FA290C1.9080808@univ-nantes.fr>

Hi Yann,

Sorry for the late response.

On 05/03/2012 07:05 AM, Yann Dupont wrote:
> Hello. I'm stress testing ceph since some time now, with quite good
> results. I really like ceph and will probably use in in some
> pre-production services.
>
> Anyway I've seen some bugs.
>
> One of them is instability if the kernel is running inside KVM, leading
> to a very fast (and reproductible) kernel oops. On bare metal this
> particular oops doesn't happen.
>
> The kernel oops itself involve ceph, but it could be a real bug in kvm too.
>
> The host machine is runnning 3.2.2
> kvm is quite ancien (0.14)
> guest OS is ubuntu 12.04 with his standard kernel. Retried with custom
> 3.2 kernel with the same problem.

I'm not sure how many people are using the kernel client within kvm,
but I haven't seen this problem before. Since it's in d_prune, it's
probably Ceph related, but perhaps kvm makes a race condition trigger
more often in your environment.

I filed http://tracker.newdream.net/issues/2444 to track this.

  reply	other threads:[~2012-05-17 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 14:05 reproductible kernel oops with kernel 3.2 inside kvm Yann Dupont
2012-05-17 22:21 ` Josh Durgin [this message]
2012-05-21 12:24   ` Yann Dupont

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=4FB57A03.70309@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=Yann.Dupont@univ-nantes.fr \
    --cc=ceph-devel@vger.kernel.org \
    /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.