linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs and load (sys)
Date: Fri, 02 Dec 2011 15:27:58 +1100	[thread overview]
Message-ID: <4ED853CE.50200@csamuel.org> (raw)
In-Reply-To: <CAJ1PRS=GGMtAsNaLyvOWL-nuRr6x1e2pj56hDqZWDFo60yNm9Q@mail.gmail.com>

On 02/12/11 15:14, krzf83@gmail.com wrote:

> I've upgraded to newest kernel 3.1.2 but problem is not fixed. 

As btrfs is an experimental filesystem I don't believe that fixes are
backported to those stable releases, they only go into Linus's tree for
his next release (3.2 in this case).  So I'm afraid if you want to pick
up fixes as they appear you'll need to track Linus's tree really (or one
of Chris's).

I guess once btrfs is stable then that'll start to happen, but for the
moment I get the feeling that fixes and features are so tightly
entangled that it would be an awful lot of work to backport them to the
older code in the last stable release.

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

      reply	other threads:[~2011-12-02  4:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 14:43 btrfs and load (sys) krzf83@gmail.com 
2011-11-23 14:56 ` Roman Mamedov
2011-11-23 15:08   ` krzf83@gmail.com 
2011-11-23 15:17     ` krzf83@gmail.com 
2011-11-24  1:00     ` Chris Samuel
2011-11-24  1:11       ` Fajar A. Nugraha
2011-11-25  4:40       ` Chris Samuel
2011-11-23 17:01 ` Phillip Susi
2011-11-24  0:42   ` krzf83@gmail.com 
2011-12-02  4:14   ` krzf83@gmail.com 
2011-12-02  4:27     ` Chris Samuel [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=4ED853CE.50200@csamuel.org \
    --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;
as well as URLs for NNTP newsgroup(s).