From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: unexplainable corruptions 3.17.0
Date: Mon, 20 Oct 2014 20:14:12 +1100 [thread overview]
Message-ID: <2588267.pfc4WIxGVz@quad> (raw)
In-Reply-To: <12404322.5f6czpaAWj@fb07-iapwap2>
On Mon, 20 Oct 2014 10:01:56 AM Marc Dietrich wrote:
> so fixes would be tagged earlier this way and merged automaticly.
I don't think there's a lot automatic about stable, Greg K-H merges patches
into a git tree here:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
As you can see since last night he pulled in a bunch of btrfs fixes into that
based upon what Chris Mason emailed out yesterday.
commit 2792dbfd1e02a70a8eef7e0cc3f44cb77d6c100f
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Mon Oct 20 07:08:43 2014 +0800
3.17-stable patches
added patches:
btrfs-add-missing-compression-property-remove-in-btrfs_ioctl_setflags.patch
btrfs-cleanup-error-handling-in-build_backref_tree.patch
btrfs-don-t-do-async-reclaim-during-log-replay.patch
btrfs-don-t-go-readonly-on-existing-qgroup-items.patch
btrfs-fix-a-deadlock-in-btrfs_dev_replace_finishing.patch
btrfs-fix-and-enhance-merge_extent_mapping-to-insert-best-fitted-extent-map.patch
btrfs-fix-build_backref_tree-issue-with-multiple-shared-blocks.patch
btrfs-fix-race-in-wait_sync-ioctl.patch
btrfs-fix-the-wrong-condition-judgment-about-subset-extent-map.patch
btrfs-fix-up-bounds-checking-in-lseek.patch
btrfs-try-not-to-enospc-on-log-replay.patch
btrfs-wake-up-transaction-thread-from-sync_fs-ioctl.patch
revert-btrfs-race-free-update-of-commit-root-for-ro-snapshots.patch
(there are also a bunch going in for 3.10, 3.14 and 3.16 too)
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2014-10-20 9:14 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
2014-10-19 3:01 ` Chris Samuel
2014-10-20 8:01 ` Marc Dietrich
2014-10-20 9:14 ` Chris Samuel [this message]
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=2588267.pfc4WIxGVz@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