All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: More candidates for 3.14 longterm fixes?
Date: Fri, 4 Jul 2014 13:22:02 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.07.04.13.22.02@googlemail.com> (raw)


Hi,

As Greg announced that 3.14 will be longterm I was wondering if we
can find a few more candidates for backported fixes.

So far I've had a couple handpicked and in (admittedly light) use
without problems, which apply cleanly to 3.14.10. 

Can we/should we find more?

My candidates so far:

Fix hang on error (such as ENOSPC) when writing extent pages:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/btrfs?id=61391d562229ed94899ed4b4973dc2f0c015292a

Ensure btrfs_prev_leaf doesn't miss 1 item:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/btrfs?id=337c6f6830a5ceb650eaf10d38ed8e8f496c8f61

Fix leaf corruption after __btrfs_drop_extents:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/btrfs?id=0b43e04f700bce8eecf3581612e9d3e15bf258bc

There may be more, but these are ones I picked off the list and
managed to apply without fixing up.

Since 3.14 will see continued use I think it would be great to
get a few more known knowns into a release that works reasonably well,
unlike (say) 3.15 so far.. :/

Any other suggestions or is this a terrible idea? :)

thanks
Holger


                 reply	other threads:[~2014-07-04 13:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pan.2014.07.04.13.22.02@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --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 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.