From: Kent Overstreet <kmo@daterainc.com>
To: Matthias Ferdinand <bcache@mfedv.net>
Cc: nks@daterainc.com, linux-bcache@vger.kernel.org
Subject: Re: md-raid5 with bcache member devices => kernel panic
Date: Thu, 5 Dec 2013 15:15:47 -0800 [thread overview]
Message-ID: <20131205231547.GB4054@kmo> (raw)
In-Reply-To: <20131205230813.GF1848@teapot>
On Fri, Dec 06, 2013 at 12:08:13AM +0100, Matthias Ferdinand wrote:
> On Thu, Dec 05, 2013 at 02:52:34PM -0800, Kent Overstreet wrote:
> > On Thu, Dec 05, 2013 at 10:29:13PM +0100, Matthias Ferdinand wrote:
> > Erk. I thought I was done with these bugs. Nick, do you think you could try and
> > track this down?
> >
> > Looking at this:
> > http://dl.mfedv.net/md5raid_on_bcache_panic/mdraid5_on_bcache_panic_3.12.2.txt
> >
> > that's a null pointer deref; if Matthias could get the exact line number it
> I have no idea how to do that - can you help me out on that?
>
> > Matthias - I'm running bcache on top of a raid6 at home and I've never seen
> I only get panics when I use md-raid on top of bcaches:
>
> LVM
> |
> md-raid5
> / | \
> bcache0 bcache1 bcache2
> | | |
> sdb6 sdc6 sdd6
>
> (probably an unusual setup; just playing around...)
Yeah, that is unusual. Very odd though, that setup I would definitely expect to
work.
You mentioned it's faster with bcache higher in the stack - do you have any
issues with your preferred setup?
If the bug isn't actually affecting real/preferred use cases then I'll be a lot
less concerned about it - I'm reworking how all this crap works in mainline,
maybe by 3.14 generic_make_request() will be accepting arbitrary size bios and
the code that's probably buggy here will be gone.
next prev parent reply other threads:[~2013-12-05 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:29 md-raid5 with bcache member devices => kernel panic Matthias Ferdinand
2013-12-05 22:52 ` Kent Overstreet
2013-12-05 23:08 ` Matthias Ferdinand
2013-12-05 23:15 ` Kent Overstreet [this message]
2013-12-06 0:00 ` Matthias Ferdinand
2013-12-06 3:22 ` Paul B. Henson
2013-12-08 23:53 ` Matthias Ferdinand
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=20131205231547.GB4054@kmo \
--to=kmo@daterainc.com \
--cc=bcache@mfedv.net \
--cc=linux-bcache@vger.kernel.org \
--cc=nks@daterainc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox