public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-bcache@vger.kernel.org
Subject: Bcache confirmed unsafe with 4.14.0? 4.14.1?
Date: Thu, 23 Nov 2017 23:41:12 -0800	[thread overview]
Message-ID: <20171124074112.7x7nnnqabrc3werm@merlins.org> (raw)

I have bcache | dmcrypt | btrfs, and I was upgrading to 4.14.0 when
someone told me about the corruption problems people noticed in 4.14.0

Is there an understood root cause and something to avoid to not trigger
the bug, or not so much?

I saw a bunch of patches go by and I'm not too clear if 4.14.1 is safe,
or not.

Can someone advise?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

             reply	other threads:[~2017-11-24  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24  7:41 Marc MERLIN [this message]
2017-11-24  9:22 ` Bcache confirmed unsafe with 4.14.0? 4.14.1? Pavel Goran
2017-11-24 16:29   ` Marc MERLIN
2017-11-26 13:55     ` Justin Cinkelj

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=20171124074112.7x7nnnqabrc3werm@merlins.org \
    --to=marc@merlins.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox