[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166450797717.256913.15506787519907913204.b4-ty@mit.edu>
Date: Thu, 29 Sep 2022 23:19:45 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca,
yebin10@...wei.com
Cc: "Theodore Ts'o" <tytso@....edu>, linux-kernel@...r.kernel.org,
jack@...e.cz
Subject: Re: [PATCH -next v2 0/3] Fix two potential memory leak
On Wed, 21 Sep 2022 14:40:37 +0800, Ye Bin wrote:
> Diff v2 vs v1:
> Add new patch "ext4: update 'state->fc_regions_size' after successful memory allocation"
>
> Ye Bin (3):
> ext4: fix potential memory leak in ext4_fc_record_modified_inode()
> ext4: fix potential memory leak in ext4_fc_record_regions()
> ext4: update 'state->fc_regions_size' after successful memory
> allocation
>
> [...]
Applied, thanks!
[1/3] ext4: fix potential memory leak in ext4_fc_record_modified_inode()
commit: 3edc135aaf975c6022f69c47e55f4e55981aff10
[2/3] ext4: fix potential memory leak in ext4_fc_record_regions()
commit: 87429b6248196338ae578d51ae95f2e3094f8a50
[3/3] ext4: update 'state->fc_regions_size' after successful memory allocation
commit: 24e597348a4676fb1e573faaea05eb9e6a4b422c
Best regards,
--
Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists