Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: unexplainable corruptions 3.17.0
Date: Sat, 18 Oct 2014 18:32:49 +1100	[thread overview]
Message-ID: <1798492.UPHDTB8iYW@quad> (raw)
In-Reply-To: <CAGfcS_muumP4VQTUkTTGqg=RpjWrU1A5cC+g4=dKMbdMoQvmXg@mail.gmail.com>

On Fri, 17 Oct 2014 02:09:30 PM Rich Freeman wrote:

> Just for clarity - when can we expect to see these in the kernel?

The stable kernel rules say:

https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

#  - It or an equivalent fix must already exist in Linus' tree (upstream).

So until Linus merges the revert into the mainline kernel it cannot go into a 
stable release, and he's not merged it yet.

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC



  reply	other threads:[~2014-10-18  7:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  9:17 unexplainable corruptions 3.17.0 Tomasz Torcz
2014-10-17  8:02 ` Liu Bo
2014-10-17  8:10   ` Tomasz Torcz
2014-10-17  8:17     ` Hugo Mills
2014-10-20 14:04       ` Zygo Blaxell
2014-10-20 14:52         ` Rich Freeman
2014-10-17  8:29     ` Liu Bo
2014-10-17  8:54       ` Tomasz Torcz
2014-10-17 12:53         ` Chris Mason
2014-10-17 18:09           ` Rich Freeman
2014-10-18  7:32             ` Chris Samuel [this message]
2014-10-19  3:01               ` Chris Samuel
2014-10-20  8:01               ` Marc Dietrich
2014-10-20  9:14                 ` Chris Samuel
2014-10-20 19:09           ` Tomasz Torcz
2014-10-17 11:38   ` Duncan
2014-10-17 15:07     ` Chris Murphy
2014-10-17 17:29   ` Tomasz Torcz
2014-10-17  8:17 ` Marc Dietrich
2014-10-17 15:01 ` Chris Murphy
2014-10-20 19:10   ` Tomasz Torcz

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=1798492.UPHDTB8iYW@quad \
    --to=chris@csamuel.org \
    --cc=linux-btrfs@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