linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] Btrfs: prevent qgroup config corruption by qgroup destroy
Date: Thu, 17 Jan 2013 09:22:07 +0100	[thread overview]
Message-ID: <cover.1358410295.git.sensille@gmx.net> (raw)

When destroying an active qgroup with qgroup destroy, the internal config will
become corrupt. This series adds 2 fixes: the first add a recovery, if the config
is already corrupt, and the second prevents the destroy if it is still active.


Arne Jansen (2):
  btrfs: ignore orphan qgroup relations
  btrfs: prevent qgroup destroy when there are still relations

 fs/btrfs/qgroup.c |   20 +++++++++++++++++++-
 1 files changed, 19 insertions(+), 1 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2013-01-17  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  8:22 Arne Jansen [this message]
2013-01-17  8:22 ` [PATCH 1/2] Btrfs: ignore orphan qgroup relations Arne Jansen
2013-01-17  8:22 ` [PATCH 2/2] Btrfs: prevent qgroup destroy when there are still relations Arne Jansen

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.1358410295.git.sensille@gmx.net \
    --to=sensille@gmx.net \
    --cc=chris.mason@fusionio.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).