From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Vasiliy Tolstov <v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>
Cc: Gabriel de Perthuis
<g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
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 16:35:51 -0700 [thread overview]
Message-ID: <20131014233551.GM28572@kmo> (raw)
In-Reply-To: <CACaajQubbRDdewAxXekeTFu-vACRb3QnN2H1cA0XOvCzeFdbcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Oct 15, 2013 at 12:41:02AM +0400, Vasiliy Tolstov wrote:
> 2013/10/14 Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> > 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.
>
>
> does branche http://evilpiepirate.org/git/linux-bcache.git/log/?h=bcache-for-3.11
> has all fixes and stable for use?
No - but 3.11.5 is out and has the fix
next prev parent reply other threads:[~2013-10-14 23:35 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
[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 [this message]
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=20131014233551.GM28572@kmo \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=i.gnatenko.brain-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@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