From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: guihc.fnst@cn.fujitsu.com, quwenruo@cn.fujitsu.com,
miaoxie@huawei.com, David Sterba <dsterba@suse.cz>,
clm@fb.com
Subject: [PULL] [PATCH 0/3] Btrfs, fixes for freezing vs pending changes
Date: Tue, 20 Jan 2015 19:05:27 +0100 [thread overview]
Message-ID: <cover.1421776294.git.dsterba@suse.cz> (raw)
There was some churn regarding the patches to $SUBJ, here's what I think is
enough to fix it for 3.19.
It's based on top of my other patch "btrfs: sync ioctl, handle errors after
transaction start" that might land in Chris' for-linus already so it's not
included here.
The patches are for review by the involved people, also available in this
branch:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
David Sterba (1):
btrfs: remove a no-op unfreeze superbock callback
Qu Wenruo (2):
btrfs: Fix the bug that fs_info->pending_changes is never cleared.
btrfs: Don't call btrfs_start_transaction() on frozen fs to avoid
deadlock.
fs/btrfs/super.c | 16 ++++++++++------
fs/btrfs/transaction.c | 2 +-
2 files changed, 11 insertions(+), 7 deletions(-)
--
2.1.3
next reply other threads:[~2015-01-20 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 18:05 David Sterba [this message]
2015-01-20 18:05 ` [PATCH 1/3] btrfs: Fix the bug that fs_info->pending_changes is never cleared David Sterba
2015-01-20 18:05 ` [PATCH 2/3] btrfs: Don't call btrfs_start_transaction() on frozen fs to avoid deadlock David Sterba
2015-01-20 18:05 ` [PATCH 3/3] btrfs: remove a no-op unfreeze superbock callback David Sterba
2015-01-23 2:32 ` [PULL] [PATCH 0/3] Btrfs, fixes for freezing vs pending changes Qu Wenruo
2015-01-23 16:07 ` David Sterba
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=cover.1421776294.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=quwenruo@cn.fujitsu.com \
/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.