All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
To: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Joseph Glanville
	<joseph.glanville-2MxvZkOi9dvvnOemgxGiVw@public.gmane.org>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Kernel panic with current bcache-3.2 branch.
Date: Fri, 17 Aug 2012 01:23:32 +0100	[thread overview]
Message-ID: <502D8F04.4010502@abpni.co.uk> (raw)
In-Reply-To: <502D8E28.9090401-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>

On 17/08/2012 01:19, Jonathan Tripathy wrote:
> On 17/08/2012 00:34, Kent Overstreet wrote:
>> On Thu, Aug 16, 2012 at 06:51:15PM +1000, Joseph Glanville wrote:
>>> Hi list, Kent,
>>>
>>> I caused a crash with the current 3.2 branch under Xen dom0.
>>> By the look of it the swap LV caused the crash?
>> Argh. Strange bug.
>>
>> I wonder if this is related to a bug someone on lkml noticed the other
>> day in my change to the dm code... I see you've got dm_multipath linked
>> in. That would cause memory corruption (underruning allocated memory),
>> which might cause this.
>>
>> I'm going to try and reproduce it too, it might be something simpler.
>> How are things configured? I see raid1 in the call stack, but there must
>> be something else too because raid1 doesn't call bio_pair_split().
>>
> Just to let you guys know that I'm currently compiling the bcache-3.2 
> branch as I type this and will be testing bcache on a Xen Dom0 test 
> bed over the next few weeks. OS is Ubuntu 12.04.x86_64. Xen version 
> will be whatever is in the Ubuntu universe repo (4.1.2). Kent, thanks 
> for your commit within the last hour. Was this to fix Joseph's problem?
>
> Thanks
> -- 
>
I should also add that my backend spindle storage is a MD RAID10 array. 
My to-be cache device is a MD RAID1 array of 2 SSD drives.

Cheers

  parent reply	other threads:[~2012-08-17  0:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  8:51 Kernel panic with current bcache-3.2 branch Joseph Glanville
     [not found] ` <CAOzFzEiS3MWe39C+XinBP3fN-Kw8Hs6n3oyqixrMVZpsuMhLcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16 11:34   ` Joseph Glanville
     [not found]     ` <CAOzFzEim7Q7eDr2z=BNsgnUuYH-XJaCPYpeVt5zkE1kvxZn+RQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16 12:07       ` Joseph Glanville
     [not found]         ` <CAOzFzEhJ1PtpbKTbkh=8XTNDdFnjgWP6qBCwQHzXhO8C9s-eyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16 23:36           ` Kent Overstreet
     [not found]             ` <20120816233600.GB26564-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-08-17  4:07               ` Joseph Glanville
2012-08-16 23:34   ` Kent Overstreet
     [not found]     ` <20120816233457.GA26564-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-08-17  0:19       ` Jonathan Tripathy
     [not found]         ` <502D8E28.9090401-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-17  0:23           ` Jonathan Tripathy [this message]
2012-08-17  4:06       ` Joseph Glanville

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=502D8F04.4010502@abpni.co.uk \
    --to=jonnyt-nf8s+5hnwl710xsdtd+oqa@public.gmane.org \
    --cc=joseph.glanville-2MxvZkOi9dvvnOemgxGiVw@public.gmane.org \
    --cc=koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.