linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>, <dsterba@suse.com>, <clm@fb.com>
Subject: Re: [PATCH 0/9 PULL REQUEST] Qgroup fixes for 4.11
Date: Mon, 6 Mar 2017 16:08:41 +0800	[thread overview]
Message-ID: <c11675d5-dd41-955c-06d0-db8aea1c7331@cn.fujitsu.com> (raw)
In-Reply-To: <20170227071039.8335-1-quwenruo@cn.fujitsu.com>

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.

Thanks,
Qu

At 02/27/2017 03:10 PM, Qu Wenruo wrote:
> Pull request can be fetched from my github:
> https://github.com/adam900710/linux.git qgroup_fixes_for_4.11
>
> The base is 6288d6eabc7505f42dda34a2c2962f91914be3a4.
> Author: Liu Bo <bo.li.liu@oracle.com>
> Date:   Tue Feb 21 12:12:58 2017 -0800
>
>     Btrfs: use the correct type when creating cow dio extent
>
> These patches are already in mail list for almost 3 months.
> For example the tracepoint patch is last updated at 2016/12/09.
>
> With this patchset btrfs can pass all xfstest qgroup tests now.
>
> This pull request should be good for 4.11 as they are all bug fixes and
> has been delayed for several times.
>
> I don't know if these patchset will be delayed again if someone wants to
> cleanup something else, and cause rebase conflicts to delay such fixes.
> But I must say, that's very frustrating to see bug fixes just get dropped
> again and again just due to new cleanups and lack of reviewers.
>
> Despite all these pities, this pull request includes:
> 1) Fix for inode_cache mount option
>    Although no one really cares inode_cache mount option, it will screw
>    qgroup for a long time.
>    Not only it will screw up qgroup test uses golden output, but also
>    new test cases use btrfsck to verify qgroup.
>
> 2) Fix for btrfs/104 kernel warning
>    This is caused by quota enabling with dirty buffers not written to
>    disc.
>
>    Fixed by checking EXTENT_QGROUP_RESERVED flag other than just
>    decreasing qgroup->reserved.
>
> 3) Fix qgroup underflow caused by freeing ranges not reserved by caller
>    Mainly exposed by Chandan on PPC64.
>
>    It's possible that buffered write is blocked by reserving metadata,
>    and in error path we will release reserved space for both data and
>    metadata.
>
>    However the reserved data can already be reserved by another process
>    writing the same page.
>
>    In that case, data reserved space can be freed by two process, one
>    for error path, one for normal write routine, causing underflow.
>
>    Fixed by checking if that data range is reserved by ourselves and
>    only free it if it's reserved by ourselves.
>
> Update since 2016/12/09:
>   Rebased to latest for-linux-4.11.
>
>   Add missing reviewed-by and tested-by tags.
>
>   Add more comment for btrfs_qgroup_reserve_data() for error handling.
>
>   Add more comment for qgroup_free_reserved_data() for later
>   enhancement (not function enhancement).
>
> Qu Wenruo (9):
>   btrfs: qgroup: Add trace point for qgroup reserved space
>   btrfs: qgroup: Re-arrange tracepoint timing to co-operate with
>     reserved space tracepoint
>   btrfs: qgroup: Fix qgroup corruption caused by inode_cache mount
>     option
>   btrfs: qgroup: Add quick exit for non-fs extents
>   btrfs: qgroup: Cleanup btrfs_qgroup_prepare_account_extents function
>   btrfs: qgroup: Return actually freed bytes for qgroup release or free
>     data
>   btrfs: qgroup: Fix qgroup reserved space underflow caused by buffered
>     write and quota enable
>   btrfs: qgroup: Introduce extent changeset for qgroup reserve functions
>   btrfs: qgroup: Fix qgroup reserved space underflow by only freeing
>     reserved ranges
>
>  fs/btrfs/ctree.h             |  12 ++-
>  fs/btrfs/extent-tree.c       |  31 +++---
>  fs/btrfs/extent_io.h         |  14 ++-
>  fs/btrfs/file.c              |  46 +++++----
>  fs/btrfs/inode-map.c         |   6 +-
>  fs/btrfs/inode.c             |  64 +++++++++----
>  fs/btrfs/ioctl.c             |  11 ++-
>  fs/btrfs/qgroup.c            | 221 ++++++++++++++++++++++++++++++++-----------
>  fs/btrfs/qgroup.h            |  14 +--
>  fs/btrfs/relocation.c        |  13 ++-
>  fs/btrfs/transaction.c       |  21 ++--
>  include/trace/events/btrfs.h |  43 +++++++++
>  12 files changed, 358 insertions(+), 138 deletions(-)
>



  parent reply	other threads:[~2017-03-06  8:22 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 ` Qu Wenruo [this message]
2017-03-06 16:44   ` [PATCH 0/9 PULL REQUEST] Qgroup fixes for 4.11 David Sterba
2017-03-06 17:56     ` Chris Mason
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=c11675d5-dd41-955c-06d0-db8aea1c7331@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.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).