From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Igor Gnatenko
<i.gnatenko.brain-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [BUG] unable to handle kernel NULL pointer dereference at 000000000000006c (bch_insert_data)
Date: Mon, 14 Oct 2013 14:38:12 +0200 [thread overview]
Message-ID: <525BE5B4.6000003@gmail.com> (raw)
In-Reply-To: <1381699461.2306.6.camel-aTCQVLFAsbFNyYP8qUDXA8/Rnsmy/zvw/z7RTEddyNg@public.gmane.org>
> On testday we found: https://bugzilla.redhat.com/show_bug.cgi?id=1018615
> which have dmesg after sysrq-t (also have some lines down).
> We setted cache_mode to writeback, mounted to foldear and started copy
> files to mounted bcache folder. It was copied some % and stayed.
> We running 3.11.4 kernel, which have fix for flushing data.
>
> [ 1550.135293] BUG: unable to handle kernel NULL pointer dereference at 000000000000006c
> [ 1550.135335] IP: [<ffffffffa04cc659>] bch_insert_data+0x19/0x30 [bcache]
That's the bug mentioned here:
http://comments.gmane.org/gmane.linux.kernel.bcache.devel/2113
http://comments.gmane.org/gmane.linux.kernel.bcache.devel/2109
http://comments.gmane.org/gmane.linux.kernel.bcache.devel/2108
It's a regression that stops writeback and made 3.11.4.
The fix is in 3.12-rc5 and will be in 3.11.5.
next prev parent reply other threads:[~2013-10-14 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 21:24 [BUG] unable to handle kernel NULL pointer dereference at 000000000000006c (bch_insert_data) Igor Gnatenko
[not found] ` <1381699461.2306.6.camel-aTCQVLFAsbFNyYP8qUDXA8/Rnsmy/zvw/z7RTEddyNg@public.gmane.org>
2013-10-14 12:38 ` Gabriel de Perthuis [this message]
[not found] ` <525BE5B4.6000003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-14 20:41 ` Vasiliy Tolstov
[not found] ` <CACaajQubbRDdewAxXekeTFu-vACRb3QnN2H1cA0XOvCzeFdbcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-14 23:35 ` Kent Overstreet
2013-10-15 9:42 ` Vasiliy Tolstov
2013-10-15 14:53 ` matthew patton
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=525BE5B4.6000003@gmail.com \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=i.gnatenko.brain-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox