From: Peter Kieser <peter@kieser.ca>
To: Andrew Thrift <andrew@networklabs.co.nz>, linux-bcache@vger.kernel.org
Cc: Greg KH <greg@kroah.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: Fwd: Bcache Status
Date: Mon, 12 Oct 2015 09:36:12 -0700 [thread overview]
Message-ID: <561BE17C.5020402@kieser.ca> (raw)
In-Reply-To: <CAEC_uJM_CZbxdMyPct0=Mc4CMzY5u4HYhzQA48dtG7kqfSi_Pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On 2015-10-11 4:04 PM, Andrew Thrift wrote:
> I notice over the past 18 months there have been a number of patches
> posted to this mailing list to resolve known issues with bcache.
>
> I cant see that these have been merged into the main bcache git at
> http://evilpiepirate.org/git/linux-bcache.git, is this actually the
> case or am I mistaken?
>
> Will these patches ever be seen in mainline ?
Backports of critical bug fixes not being done was brought to attention
of Greg KH in September 2014, where Jens and myself mentioned that
bcache stable patches (data corruption, stability, etc.) were not being
backported to the Linux stable branches. The response from the author of
bcache was "This kind of unnecessary hostility is why I don't bother
with stable much anymore. I get enough of this bullshit at work, thank you."
Unfortunately, the situation hasn't cahnged. bcache still will eat your
data under certain use cases, and there is no warning and bcache still
doesn't have a testing/experimental flag set on it. I guess the ultimate
answer was "backport and submit a pull request yourself" but I'm not
sure this is appropriate.
-Peter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4311 bytes --]
next prev parent reply other threads:[~2015-10-12 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEC_uJOv7gmb3ddTa0yNHDXHPbX_0Mr2uZsDGM2iNMSrPKex4A@mail.gmail.com>
2015-10-11 23:04 ` Fwd: Bcache Status Andrew Thrift
2015-10-12 16:36 ` Peter Kieser [this message]
2015-10-12 16:51 ` Vasiliy Tolstov
2015-10-14 8:42 ` Koen Kooi
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=561BE17C.5020402@kieser.ca \
--to=peter@kieser.ca \
--cc=andrew@networklabs.co.nz \
--cc=axboe@kernel.dk \
--cc=greg@kroah.com \
--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 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.