From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: matthew patton <pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: bcache oops in bch_insert_data with the latest stables fixes (3.10.15)
Date: Wed, 09 Oct 2013 00:48:29 +0200 [thread overview]
Message-ID: <52548BBD.9060601@gmail.com> (raw)
In-Reply-To: <1381271982.70536.YahooMailNeo-XYahOdtEMNnuQS8rMknbopOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
Le mer. 09 oct. 2013 00:39:42 CEST, matthew patton a écrit :
> I'm confused as to what tree is actually safe to use. When these and
> like messages go out are all of the 3.10, 3.11, 3.12 etc trees
> updated to kill the bad code? There seems to be a lot of churn and as
> a user I'm not sure what code-base to grab that has the
> recent/obscure bugs fixed, and which are time-bombs.
>
> Do all of the 3.10.x Linux kernel sources work with the bcache
> 3.10-stable git branch? Does 3.10-stable have *ALL* of the recent bug
> fixes included? If not, why not? Same for 3.11 and friends.
>
> A little guidance please?
3.11.4 minus the patch I mentioned is fine in my experience; I've been
running it for a while along with other people (through the
bcache-for-3.11 branch). I'm not sure what corruption that patch was
meant to prevent; I haven't encountered it as far as I know.
next prev parent reply other threads:[~2013-10-08 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 10:38 bcache oops in bch_insert_data with the latest stables fixes (3.10.15) Cyril B.
[not found] ` <52513DBD.80005-SxHCd5+OuqTrt3ojHgZu+w@public.gmane.org>
2013-10-06 15:50 ` Gabriel de Perthuis
2013-10-08 22:13 ` Gabriel de Perthuis
[not found] ` <525483A4.5020607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-08 22:32 ` Kent Overstreet
2013-10-09 21:25 ` Greg KH
2013-10-11 7:07 ` Kent Overstreet
2013-10-11 15:51 ` Greg KH
2013-10-08 22:39 ` matthew patton
[not found] ` <1381271982.70536.YahooMailNeo-XYahOdtEMNnuQS8rMknbopOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-08 22:48 ` Gabriel de Perthuis [this message]
[not found] ` <52548BBD.9060601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-09 7:41 ` Alfredo Sola
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=52548BBD.9060601@gmail.com \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pattonme-/E1597aS9LQAvxtiuMwx3w@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.