From: Ilya Dryomov <idryomov@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@fusionio.com>,
Stefan Behrens <sbehrens@giantdisaster.de>
Subject: Re: [PATCH 0/5] Mutually exclusive ops fixes
Date: Sun, 20 Jan 2013 17:28:25 +0200 [thread overview]
Message-ID: <20130120152825.GA1919@zambezi.lan> (raw)
In-Reply-To: <1358695352-7140-1-git-send-email-idryomov@gmail.com>
On Sun, Jan 20, 2013 at 05:22:27PM +0200, Ilya Dryomov wrote:
> Hello,
>
> This is a set of fixes for mutually exclusive ops stuff added by Stefan
> as part of the dev-replace patchset. The main one here is the first
> patch, it fixes a regression in balancing interface. The second patch
> brings EINVAL error code back. The rest are relatively minor ordering
> fixes.
You can pull from
git://github.com/idryomov/btrfs-unstable.git mutex-ops@next-master
top commit 2f68aafa90fedb3cdb80f0a8517a2130c5c035b0
Thanks,
Ilya
next prev parent reply other threads:[~2013-01-20 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 15:22 [PATCH 0/5] Mutually exclusive ops fixes Ilya Dryomov
2013-01-20 15:22 ` [PATCH 1/5] Btrfs: bring back balance pause/resume logic Ilya Dryomov
2013-01-20 15:22 ` [PATCH 2/5] Btrfs: fix "mutually exclusive op is running" error code Ilya Dryomov
2013-01-20 15:22 ` [PATCH 3/5] Btrfs: fix unlock order in btrfs_ioctl_resize Ilya Dryomov
2013-01-20 15:22 ` [PATCH 4/5] Btrfs: fix unlock order in btrfs_ioctl_rm_dev Ilya Dryomov
2013-01-20 15:22 ` [PATCH 5/5] Btrfs: reorder locks and sanity checks in btrfs_ioctl_defrag Ilya Dryomov
2013-01-20 15:28 ` Ilya Dryomov [this message]
2013-01-21 12:25 ` [PATCH 0/5] Mutually exclusive ops fixes 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=20130120152825.GA1919@zambezi.lan \
--to=idryomov@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).