From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca, yebin10@huawei.com
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH -next v2 0/3] Fix two potential memory leak
Date: Thu, 29 Sep 2022 23:19:45 -0400 [thread overview]
Message-ID: <166450797717.256913.15506787519907913204.b4-ty@mit.edu> (raw)
In-Reply-To: <20220921064040.3693255-1-yebin10@huawei.com>
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@mit.edu>
prev parent reply other threads:[~2022-09-30 3:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:40 [PATCH -next v2 0/3] Fix two potential memory leak Ye Bin
2022-09-21 6:40 ` [PATCH -next v2 1/3] ext4: fix potential memory leak in ext4_fc_record_modified_inode() Ye Bin
2022-09-21 11:31 ` Jan Kara
2022-09-21 6:40 ` [PATCH -next v2 2/3] ext4: fix potential memory leak in ext4_fc_record_regions() Ye Bin
2022-09-21 11:32 ` Jan Kara
2022-09-21 6:40 ` [PATCH -next v2 3/3] ext4: update 'state->fc_regions_size' after successful memory allocation Ye Bin
2022-09-21 11:32 ` Jan Kara
2022-09-21 16:38 ` Damien Guibouret
2022-09-30 3:19 ` Theodore Ts'o [this message]
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=166450797717.256913.15506787519907913204.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin10@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.