]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
efivarfs: revert "fix memory leak in efivarfs_create()"
authorArd Biesheuvel <ardb@kernel.org>
Wed, 25 Nov 2020 07:45:55 +0000 (08:45 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 2 Dec 2020 07:34:44 +0000 (08:34 +0100)
commit2f195f0ecb2dd38f4bb952d14217a10f4f1cc520
treed1a33145b3b14c5f3c2e30a60d7b87abdfab11af
parent7e0abaac82064277883b7063333ddbdfadac8a00
efivarfs: revert "fix memory leak in efivarfs_create()"

[ Upstream commit ff04f3b6f2e27f8ae28a498416af2a8dd5072b43 ]

The memory leak addressed by commit fe5186cf12e3 is a false positive:
all allocations are recorded in a linked list, and freed when the
filesystem is unmounted. This leads to double frees, and as reported
by David, leads to crashes if SLUB is configured to self destruct when
double frees occur.

So drop the redundant kfree() again, and instead, mark the offending
pointer variable so the allocation is ignored by kmemleak.

Cc: Vamshi K Sthambamkadi <vamshi.k.sthambamkadi@gmail.com>
Fixes: fe5186cf12e3 ("efivarfs: fix memory leak in efivarfs_create()")
Reported-by: David Laight <David.Laight@aculab.com>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/efivarfs/inode.c
fs/efivarfs/super.c