ext4: fix a memory leak of ext4_free_data
authorChunguang Xu <brookxu@tencent.com>
Sat, 7 Nov 2020 15:58:18 +0000 (23:58 +0800)
committerTheodore Ts'o <tytso@mit.edu>
Thu, 17 Dec 2020 18:30:09 +0000 (13:30 -0500)
commitcca415537244f6102cbb09b5b90db6ae2c953bdd
tree8dce47d4ded574925459bcc9eb47808063a9171b
parent41fca96e635be523c28b8d57f2d1b1e51d1221d8
ext4: fix a memory leak of ext4_free_data

When freeing metadata, we will create an ext4_free_data and
insert it into the pending free list.  After the current
transaction is committed, the object will be freed.

ext4_mb_free_metadata() will check whether the area to be freed
overlaps with the pending free list. If true, return directly. At this
time, ext4_free_data is leaked.  Fortunately, the probability of this
problem is small, since it only occurs if the file system is corrupted
such that a block is claimed by more one inode and those inodes are
deleted within a single jbd2 transaction.

Signed-off-by: Chunguang Xu <brookxu@tencent.com>
Link: https://lore.kernel.org/r/1604764698-4269-8-git-send-email-brookxu@tencent.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
fs/ext4/mballoc.c