From: "Theodore Ts'o" <tytso@mit.edu>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz,
adilger.kernel@dilger.ca, miaoxie@huawei.com
Subject: Re: [PATCH v2 1/2] ext4: brelse all indirect buffer in ext4_ind_remove_space()
Date: Sat, 23 Mar 2019 11:53:49 -0400 [thread overview]
Message-ID: <20190323155349.GC5675@mit.edu> (raw)
In-Reply-To: <1552633813-42832-2-git-send-email-yi.zhang@huawei.com>
On Fri, Mar 15, 2019 at 03:10:12PM +0800, zhangyi (F) wrote:
> All indirect buffers get by ext4_find_shared() should be released no
> mater the branch should be freed or not. But now, we forget to release
> the lower depth indirect buffers when removing space from the same
> higher depth indirect block. It will lead to buffer leak and futher
> more, it may lead to quota information corruption when using old quota,
> consider the following case.
>
> - Create and mount an empty ext4 filesystem without extent and quota
> features,
> - quotacheck and enable the user & group quota,
> - Create some files and write some data to them, and then punch hole
> to some files of them, it may trigger the buffer leak problem
> mentioned above.
> - Disable quota and run quotacheck again, it will create two new
> aquota files and write the checked quota information to them, which
> probably may reuse the freed indirect block(the buffer and page
> cache was not freed) as data block.
> - Enable quota again, it will invoke
> vfs_load_quota_inode()->invalidate_bdev() to try to clean unused
> buffers and pagecache. Unfortunately, because of the buffer of quota
> data block is still referenced, quota code cannot read the up to date
> quota info from the device and lead to quota information corruption.
>
> This problem can be reproduced by xfstests generic/231 on ext3 file
> system or ext4 file system without extent and quota features.
>
> This patch fix this problem by brelse the missing indirect buffers, in
> ext4_ind_remove_space().
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
> Suggested-by: Jan Kara <jack@suse.cz>
> Cc: <stable@vger.kernel.org>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2019-03-23 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 7:10 [PATCH v2 0/2] ext4: fix buffer references leak problem zhangyi (F)
2019-03-15 7:10 ` [PATCH v2 1/2] ext4: brelse all indirect buffer in ext4_ind_remove_space() zhangyi (F)
2019-03-18 11:08 ` Jan Kara
2019-03-23 15:53 ` Theodore Ts'o [this message]
2019-03-15 7:10 ` [PATCH v2 2/2] ext4: cleanup bh release code " zhangyi (F)
2019-03-18 11:10 ` Jan Kara
2019-03-23 15:58 ` Theodore Ts'o
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=20190323155349.GC5675@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=yi.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).