[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoWnHXZSQZA4CL6+@mit.edu>
Date: Wed, 18 May 2022 22:10:37 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-fscrypt@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
Jeff Layton <jlayton@...nel.org>,
Lukas Czerner <lczerner@...hat.com>,
Jaegeuk Kim <jaegeuk@...nel.org>, stable@...r.kernel.org
Subject: Re: [PATCH v3 1/5] ext4: fix memory leak in
parse_apply_sb_mount_options()
On Fri, May 13, 2022 at 04:16:01PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> If processing the on-disk mount options fails after any memory was
> allocated in the ext4_fs_context, e.g. s_qf_names, then this memory is
> leaked. Fix this by calling ext4_fc_free() instead of kfree() directly.
>
> Reproducer:
>
> mkfs.ext4 -F /dev/vdc
> tune2fs /dev/vdc -E mount_opts=usrjquota=file
> echo clear > /sys/kernel/debug/kmemleak
> mount /dev/vdc /vdc
> echo scan > /sys/kernel/debug/kmemleak
> sleep 5
> echo scan > /sys/kernel/debug/kmemleak
> cat /sys/kernel/debug/kmemleak
>
> Fixes: 7edfd85b1ffd ("ext4: Completely separate options parsing and sb setup")
> Cc: stable@...r.kernel.org
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Thanks, applied.
- Ted
Powered by blists - more mailing lists