linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: linux-bcache@vger.kernel.org
Subject: Re: Fwd: Bcache Status
Date: Wed, 14 Oct 2015 10:42:48 +0200	[thread overview]
Message-ID: <mvl4i8$k8v$1@ger.gmane.org> (raw)
In-Reply-To: <561BE17C.5020402@kieser.ca>

Op 12-10-15 om 18:36 schreef Peter Kieser:
> 
> 
> 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.

If Kent won't do it (for whatever reasons), anyone can propose the patches for
backporting to the various stable kernels.

This is a seperate problem than the "patches posted to this list don't get
into mainline at all" issue.

      parent reply	other threads:[~2015-10-14  8:45 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
2015-10-12 16:51     ` Vasiliy Tolstov
2015-10-14  8:42     ` Koen Kooi [this message]

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='mvl4i8$k8v$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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;
as well as URLs for NNTP newsgroup(s).