From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, rgoldwyn@suse.de
Subject: Re: [PATCH] btrfs: qgroups: Fix BUG_ON condition
Date: Wed, 12 Jul 2017 15:09:42 +0800 [thread overview]
Message-ID: <9f2efc65-1972-e200-72ff-2ccf29da06d1@gmx.com> (raw)
In-Reply-To: <1499841739-18549-1-git-send-email-nborisov@suse.com>
在 2017年07月12日 14:42, Nikolay Borisov 写道:
> The current code was erroneously checking for root_level > BTRFS_MAX_LEVEL. If
> we had a root_level of 8 then the check won't trigger and we could
> potentially hit a buffer overflow. The correct check should be
> root_level >= BTRFS_MAX_LEVEL
Thanks for catching this.
Reviewed-by: Qu Wenruo <quwenruo.btrfs@gmx.com>
>
> Signed-off-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 4ce351efe281..3b787915ef31 100644
> --- a/fs/btrfs/qgroup.c
> +++ b/fs/btrfs/qgroup.c
> @@ -1603,7 +1603,7 @@ int btrfs_qgroup_trace_subtree(struct btrfs_trans_handle *trans,
> struct extent_buffer *eb = root_eb;
> struct btrfs_path *path = NULL;
>
> - BUG_ON(root_level < 0 || root_level > BTRFS_MAX_LEVEL);
> + BUG_ON(root_level < 0 || root_level >= BTRFS_MAX_LEVEL);
> BUG_ON(root_eb == NULL);
>
> if (!test_bit(BTRFS_FS_QUOTA_ENABLED, &fs_info->flags))
> @@ -2959,7 +2959,7 @@ static int __btrfs_qgroup_release_data(struct inode *inode,
> if (free && reserved)
> return qgroup_free_reserved_data(inode, reserved, start, len);
> extent_changeset_init(&changeset);
> - ret = clear_record_extent_bits(&BTRFS_I(inode)->io_tree, start,
> + ret = clear_record_extent_bits(&BTRFS_I(inode)->io_tree, start,
> start + len -1, EXTENT_QGROUP_RESERVED, &changeset);
I didn't recongize it's a tailing white space at first.
Nice catch.
Thanks,
Qu
> if (ret < 0)
> goto out;
>
next prev parent reply other threads:[~2017-07-12 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:42 [PATCH] btrfs: qgroups: Fix BUG_ON condition Nikolay Borisov
2017-07-12 7:09 ` Qu Wenruo [this message]
2017-07-12 13:42 ` David Sterba
2017-07-12 13:50 ` Nikolay Borisov
2017-07-12 13:51 ` David Sterba
2017-07-12 14:11 ` Qu Wenruo
2017-07-12 14:00 ` Qu Wenruo
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=9f2efc65-1972-e200-72ff-2ccf29da06d1@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=rgoldwyn@suse.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