linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH v4 0/3] btrfs: Fix lost-data-profile caused by auto removing bg and balance bg
Date: Thu, 8 Oct 2015 18:59:52 +0800	[thread overview]
Message-ID: <cover.1444301651.git.zhaolei@cn.fujitsu.com> (raw)

Changelog v3->v4:
1: Avoid down_read() in spin_lock context.
   Noticed-by: Chris Mason <clm@fb.com>

Changelog v2->v3:
1: Use list_is_singular() instead of
   block_group->list.next == block_group->list.prev
   Suggested-by: Jeff Mahoney <jeffm@suse.com>
2: Add Reviewed-by: Filipe Manana <fdmanana@suse.com>

Changelog v1->v2:
1: Put code of checking block_group->list into
   semaphore of space_info->groups_sem.
   Noticed-by: Filipe Manana <fdmanana@gmail.com>
2: Update patch description of "Fix" field
3: Use BTRFS_BLOCK_GROUP_DATA for btrfs_force_chunk_alloc
   instead of 1
4: Only reserve chunk when doing balance on data chunk.
All suggested-by: Filipe Manana <fdmanana@gmail.com>

Zhao Lei (3):
  btrfs: Fix lost-data-profile caused by auto removing bg
  btrfs: Fix lost-data-profile caused by balance bg
  btrfs: Use fs_info directly in btrfs_delete_unused_bgs

 fs/btrfs/extent-tree.c | 11 +++++++----
 fs/btrfs/volumes.c     | 24 ++++++++++++++++++++++++
 2 files changed, 31 insertions(+), 4 deletions(-)

-- 
1.8.5.1


             reply	other threads:[~2015-10-08 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 10:59 Zhao Lei [this message]
2015-10-08 10:59 ` [PATCH v4 1/3] btrfs: Fix lost-data-profile caused by auto removing bg Zhao Lei
2015-10-08 10:59 ` [PATCH v4 2/3] btrfs: Fix lost-data-profile caused by balance bg Zhao Lei
2015-10-08 10:59 ` [PATCH v4 3/3] btrfs: Use fs_info directly in btrfs_delete_unused_bgs Zhao Lei

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.1444301651.git.zhaolei@cn.fujitsu.com \
    --to=zhaolei@cn.fujitsu.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 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).