From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/2] btrfs: qgroup: Fix wrong parameter order for trace events
Date: Thu, 17 Oct 2019 09:37:55 +0300 [thread overview]
Message-ID: <d436508c-08fc-5b61-fa41-72377e88f2c8@suse.com> (raw)
In-Reply-To: <20191017023837.32264-2-wqu@suse.com>
On 17.10.19 г. 5:38 ч., Qu Wenruo wrote:
> [BUG]
> For btrfs:qgroup_meta_reserve event, the trace event can output garbage:
> qgroup_meta_reserve: 9c7f6acc-b342-4037-bc47-7f6e4d2232d7: refroot=5(FS_TREE) type=DATA diff=2
>
> The diff should always be alinged to sector size (4k), so there is
> definitely something wrong.
>
> [CAUSE]
> For the wrong @diff, it's caused by wrong parameter order.
> The correct parameters are:
> struct btrfs_root, s64 diff, int type.
>
> However the parameters used are:
> struct btrfs_root, int type, s64 diff.
>
> [FIX]
> Fix the super stupid bug.
>
> Fixes: 4ee0d8832c2e ("btrfs: qgroup: Update trace events for metadata reservation")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/qgroup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
> index c4bb69941c77..3ad151655eb8 100644
> --- a/fs/btrfs/qgroup.c
> +++ b/fs/btrfs/qgroup.c
> @@ -3629,7 +3629,7 @@ int __btrfs_qgroup_reserve_meta(struct btrfs_root *root, int num_bytes,
> return 0;
>
> BUG_ON(num_bytes != round_down(num_bytes, fs_info->nodesize));
> - trace_qgroup_meta_reserve(root, type, (s64)num_bytes);
> + trace_qgroup_meta_reserve(root, (s64)num_bytes, type);
> ret = qgroup_reserve(root, num_bytes, enforce, type);
> if (ret < 0)
> return ret;
> @@ -3676,7 +3676,7 @@ void __btrfs_qgroup_free_meta(struct btrfs_root *root, int num_bytes,
> */
> num_bytes = sub_root_meta_rsv(root, num_bytes, type);
> BUG_ON(num_bytes != round_down(num_bytes, fs_info->nodesize));
> - trace_qgroup_meta_reserve(root, type, -(s64)num_bytes);
> + trace_qgroup_meta_reserve(root, -(s64)num_bytes, type);
> btrfs_qgroup_free_refroot(fs_info, root->root_key.objectid,
> num_bytes, type);
> }
>
next prev parent reply other threads:[~2019-10-17 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 2:38 [PATCH v2 0/2] btrfs: qgroup: Bug fixes for trace events Qu Wenruo
2019-10-17 2:38 ` [PATCH v2 1/2] btrfs: qgroup: Fix wrong parameter order " Qu Wenruo
2019-10-17 6:37 ` Nikolay Borisov [this message]
2019-10-17 2:38 ` [PATCH v2 2/2] btrfs: qgroup: Fix bad entry members of qgroup " Qu Wenruo
2019-10-17 6:33 ` Nikolay Borisov
2019-10-17 12:09 ` [PATCH v2 0/2] btrfs: qgroup: Bug fixes for " 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=d436508c-08fc-5b61-fa41-72377e88f2c8@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox