From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: <dsterba@suse.cz>, <miaoxie@huawei.com>
Subject: [PATCH RFC v3 0/5] mount options consistent enhancement
Date: Fri, 23 Jan 2015 17:31:40 +0800 [thread overview]
Message-ID: <1422005505-9472-1-git-send-email-quwenruo@cn.fujitsu.com> (raw)
Patchset to solve the previous found deadlock and enhance mount options
consistence.
Unlike previous pending_changes, which uses transaction commits to
ensure mount option doesn't change during transaction.
This patch use the RCU-like concept, which will copy the mount_opt from
fs_info into btrfs_transaction, and each btrfs_test_opt() for specific
mount option bit(SPACE_CACHE/INODE_MAP_CACHE) should be changed to
btrfs_test_trans_opt().
So mount option during transaction won't be changed, and also, no extra
read_only or freeze check is needed, the commit routine is also
untouched.
Qu Wenruo (5):
Revert "btrfs: add support for processing pending changes" related
commits
btrfs: Make btrfs_parse_options() parse mount option in a atomic way
btrfs: Introduce per-transaction mount_opt to keep mount option
consistent during transaction.
btrfs: Use btrfs_test_trans_opt() to handle SPACE_CACHE if it's under
transaction protect.
btrfs: Use btrfs_test_trans_opt() to handle INODE_CACHE if it's under
transaction protect.
fs/btrfs/ctree.h | 64 +++-------------------
fs/btrfs/disk-io.c | 6 ---
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/free-space-cache.c | 2 +-
fs/btrfs/inode-map.c | 5 +-
fs/btrfs/super.c | 129 ++++++++++++++++++++++----------------------
fs/btrfs/sysfs.c | 34 +++++++-----
fs/btrfs/transaction.c | 43 ++-------------
fs/btrfs/transaction.h | 6 ++-
9 files changed, 107 insertions(+), 184 deletions(-)
--
2.2.2
next reply other threads:[~2015-01-23 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 9:31 Qu Wenruo [this message]
2015-01-23 9:31 ` [PATCH RFC v3 1/5] Revert "btrfs: add support for processing pending changes" related commits Qu Wenruo
2015-01-23 14:57 ` David Sterba
2015-01-26 0:37 ` Qu Wenruo
2015-01-26 6:05 ` Qu Wenruo
2015-01-28 13:25 ` David Sterba
2015-01-29 1:15 ` Qu Wenruo
2015-01-30 17:30 ` David Sterba
2015-01-23 9:31 ` [PATCH RFC v3 2/5] btrfs: Make btrfs_parse_options() parse mount option in a atomic way Qu Wenruo
2015-01-23 9:31 ` [PATCH RFC v3 3/5] btrfs: Introduce per-transaction mount_opt to keep mount option consistent during transaction Qu Wenruo
2015-01-23 9:31 ` [PATCH RFC v3 4/5] btrfs: Use btrfs_test_trans_opt() to handle SPACE_CACHE if it's under transaction protect Qu Wenruo
2015-01-23 9:31 ` [PATCH RFC v3 5/5] btrfs: Use btrfs_test_trans_opt() to handle INODE_CACHE " Qu Wenruo
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=1422005505-9472-1-git-send-email-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaoxie@huawei.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 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).