public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: Gabriel de Perthuis <g2p.code@gmail.com>,
	linux stable <stable@vger.kernel.org>,
	cbay@excellency.fr,
	"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: bcache oops in bch_insert_data with the latest stables fixes (3.10.15)
Date: Wed, 9 Oct 2013 14:25:52 -0700	[thread overview]
Message-ID: <20131009212552.GA24271@kroah.com> (raw)
In-Reply-To: <20131008223221.GD7202@kmo>

On Tue, Oct 08, 2013 at 03:32:21PM -0700, Kent Overstreet wrote:
> On Wed, Oct 09, 2013 at 12:13:56AM +0200, Gabriel de Perthuis wrote:
> > Le 06/10/2013 17:50, Gabriel de Perthuis a écrit :
> > > Le 06/10/2013 12:38, Cyril B. a écrit :
> > >> Hello,
> > >>
> > >> I get the following oops immediately after booting on 3.10.15.
> > >> Everything works fine in 3.10.10. Both the backing and cache devices are
> > >> on top of mdadm.
> > > 
> > > Reverting c0f04d88e46d14de51f4baebb6efafb7d59e9f96 fixes it; it was one
> > > of the few commits that's in 3.12 and -stable but not in
> > > bcache-for-3.11.  That commit causes bch_insert_data to be called with
> > > an unset op.cache_bio.
> > 
> > Pinging stable,
> > http://git.kernel.org/linus/c0f04d88e46d14de51f4baebb6efafb7d59e9f96
> > should be reverted.  It was in 3.11.4 and 3.10.15 (and 3.12-rc3).
> > It breaks bcache's writeback mode by calling bch_writeback_data without
> > setting cache_bio (it's more visible here[1]).  There's a bit of
> > indirection through closure calls, but it could never work.
> 
> Greg - I screwed up on that patch (and I'm still scratching my head as
> to how testing missed it) - it's a two line fix I'll be mailing off to
> Linus shortly, or if you don't want to wait for that reverting it might
> be better (though there was a data corruption bug that users reported
> that fixed, so I'd be hesitent there):
> 
> Here's the fix I just mailed out, just waiting on a bit of outside
> testing to mail it to Linus:
> 
> http://permalink.gmane.org/gmane.linux.kernel.bcache.devel/2113

I'll wait for the new patch to get into Linus's tree, so as to keep
things synced up.  Let me know what the git commit it of the patch is
when hit hits his tree and I'll add it to the next stable queue.

thanks,

greg k-h

  reply	other threads:[~2013-10-09 21:25 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 [this message]
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
     [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=20131009212552.GA24271@kroah.com \
    --to=greg@kroah.com \
    --cc=cbay@excellency.fr \
    --cc=g2p.code@gmail.com \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox