From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>, Qu Wenruo <quwenruo@cn.fujitsu.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/9 PULL REQUEST] Qgroup fixes for 4.11
Date: Mon, 6 Mar 2017 12:56:13 -0500 [thread overview]
Message-ID: <8084eb83-7dc5-95b2-0eed-238add235739@fb.com> (raw)
In-Reply-To: <20170306164448.GO4662@suse.cz>
On 03/06/2017 11:44 AM, David Sterba wrote:
> On Mon, Mar 06, 2017 at 04:08:41PM +0800, Qu Wenruo wrote:
>> Any response?
>>
>> These patches are already here for at least 2 kernel releases.
>> And are all bug fixes, and fix bugs that are already reported.
>>
>> I didn't see any reason why it should be delayed for so long time.
>
> The reason is not enough review for the whole series. The delay is
> unfortunate, same as almost zero people capable & willing to review it,
> despite your efforts to keep the series up to date with current code.
>
I've been hesitated to take more series of qgroup fixes because past
sets have ended up causing problems down the line. I'm queuing it for
v4.12 while I collect tests and reviews though, it's definitely not fair
for you to have to keep rebasing it without suggestions on what to fix.
Thanks!
-chris
next prev parent reply other threads:[~2017-03-06 17:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:10 [PATCH 0/9 PULL REQUEST] Qgroup fixes for 4.11 Qu Wenruo
2017-02-27 7:10 ` [PATCH 1/9] btrfs: qgroup: Add trace point for qgroup reserved space Qu Wenruo
2017-03-07 15:19 ` David Sterba
2017-03-07 16:30 ` Jeff Mahoney
2017-03-09 6:02 ` Qu Wenruo
2017-02-27 7:10 ` [PATCH 2/9] btrfs: qgroup: Re-arrange tracepoint timing to co-operate with reserved space tracepoint Qu Wenruo
2017-03-07 19:11 ` Jeff Mahoney
2017-02-27 7:10 ` [PATCH 3/9] btrfs: qgroup: Fix qgroup corruption caused by inode_cache mount option Qu Wenruo
2017-03-07 19:21 ` Jeff Mahoney
2017-03-08 0:36 ` Qu Wenruo
2017-03-08 14:23 ` Jeff Mahoney
2017-02-27 7:10 ` [PATCH 4/9] btrfs: qgroup: Add quick exit for non-fs extents Qu Wenruo
2017-02-27 7:10 ` [PATCH 5/9] btrfs: qgroup: Cleanup btrfs_qgroup_prepare_account_extents function Qu Wenruo
2017-02-27 7:10 ` [PATCH 6/9] btrfs: qgroup: Return actually freed bytes for qgroup release or free data Qu Wenruo
2017-02-27 7:10 ` [PATCH 7/9] btrfs: qgroup: Fix qgroup reserved space underflow caused by buffered write and quota enable Qu Wenruo
2017-02-27 7:10 ` [PATCH 8/9] btrfs: qgroup: Introduce extent changeset for qgroup reserve functions Qu Wenruo
2017-02-27 7:10 ` [PATCH 9/9] btrfs: qgroup: Fix qgroup reserved space underflow by only freeing reserved ranges Qu Wenruo
2017-03-06 8:08 ` [PATCH 0/9 PULL REQUEST] Qgroup fixes for 4.11 Qu Wenruo
2017-03-06 16:44 ` David Sterba
2017-03-06 17:56 ` Chris Mason [this message]
2017-03-08 14:24 ` Jeff Mahoney
2017-03-14 13:17 ` David Sterba
2017-03-07 15:13 ` David Sterba
2017-03-08 0:28 ` Qu Wenruo
2017-03-14 13:32 ` 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=8084eb83-7dc5-95b2-0eed-238add235739@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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.