From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: Btrfs stable updates for v3.16
Date: Wed, 3 Sep 2014 23:36:00 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.03.23.36.00@googlemail.com> (raw)
In-Reply-To: 54077F27.1040603@fb.com
On Wed, 03 Sep 2014 16:50:47 -0400, Chris Mason wrote:
> Hi everyone,
>
> For 3.16, please pull these into stable, I've cherry picked and tested
> them here. For 3.15 and earlier there are a few conflicts, so I'll make
> a git tree with things to pull.
>
> 8d875f95da43c6a8f18f77869f2ef26e9594fecc v3.15+
This ("fix filemap_flush call in btrfs_file_release") is the only one
that requires some work for 3.14.
There is one conflict in ordered.data.c - just a sligh work queue
submission change - and the second in transaction.c where the patch does
not delete enough from btrfs_flush_all_pending_stuffs(), since 3.14 still
has the old qgroup calls in place. I removed it wholesale and that makes
everything fit.
The followup ("fix filemap_flush call in btrfs_file_release") then also
applies.
Should they also go into the next 3.14.x stable cycle? This rename
deadlock sounds like a possible problem with rsync, which seems like a
popular use case, and I guess nobody will complain about slightly better
performance either.
Holger
next prev parent reply other threads:[~2014-09-03 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 20:50 Btrfs stable updates for v3.16 Chris Mason
2014-09-03 21:33 ` Greg KH
2014-09-03 23:36 ` Holger Hoffstätte [this message]
2014-09-03 23:50 ` Chris Mason
2014-09-04 17:31 ` Holger Hoffstätte
2014-09-06 21:58 ` Marc MERLIN
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.09.03.23.36.00@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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.