From: Sebastian Roesner <sroesner-kernelorg@roesner-online.de>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [BUG] NULL pointer in raid1_make_request passed to bio_trim when adding md as bcache caching dev
Date: Sat, 26 Mar 2016 19:38:55 +0100 [thread overview]
Message-ID: <56F6D73F.7020305@roesner-online.de> (raw)
In-Reply-To: <alpine.LRH.2.11.1603252117250.13440@mail.ewheeler.net>
Hi Eric,
[other lists removed intentionally]
> This could be an upstream problem.
I tried to reproduce it on a test system with the same kernel with new
created superblocks, there everything worked fine. Also after setting
dev.cache.discard to yes.
Then I copied the complete partitions from the productive system and got
the same bug there.
Long story short: It seems to be caused by some data in the the
cache-device superblock. So even if it's an upstream problem, it's
somehow caused by data in my superblock.
It can be found here: https://www.f0o.de/~sroesner/bcache-superblock.bz2
Maybe you can reproduce it, for testing I created a degraded raid on
only one 500G partition and tried to register it to cause the bug.
Sebastian
next prev parent reply other threads:[~2016-03-26 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 15:19 Bug - bcache: "unable to handle kernel NULL pointer dereference" when trying to add a md caching device Sebastian Roesner
2016-03-25 1:49 ` Eric Wheeler
2016-03-25 4:18 ` Eric Wheeler
2016-03-25 14:11 ` Sebastian Roesner
2016-03-25 20:44 ` [BUG] NULL pointer in raid1_make_request passed to bio_trim when adding md as bcache caching dev Eric Wheeler
2016-03-25 21:32 ` Eric Wheeler
2016-03-26 18:38 ` Sebastian Roesner [this message]
2016-03-26 15:40 ` Ming Lei
2016-03-26 16:46 ` Sebastian Roesner
2016-03-28 18:10 ` Shaohua Li
2016-03-28 18:38 ` Jeff Moyer
2016-03-29 1:28 ` Ming Lei
2016-04-01 18:14 ` Eric Wheeler
2016-04-10 18:01 ` Sebastian Roesner
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=56F6D73F.7020305@roesner-online.de \
--to=sroesner-kernelorg@roesner-online.de \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@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.