From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: fix freeing bitmap in allocation error path
Date: Wed, 25 May 2011 19:30:45 -0400 [thread overview]
Message-ID: <20110525233045.GF9520@thunk.org> (raw)
In-Reply-To: <1300702421-4774-1-git-send-email-lczerner@redhat.com>
On Mon, Mar 21, 2011 at 11:13:41AM +0100, Lukas Czerner wrote:
> In ext2fs_alloc_generic_bmap() error path, when new bitmap allocation
> fails ext2fs_generic_bitmap should be freed, however in current state it
> first frees ext2fs_generic_bitmap and then
> ext2fs_generic_bitmap->description which is wrong. This commit fix the
> free ordering.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
This was actually pulled into e2fsprogs a while back, but it looks
like I forgot to send an e-mail ack (or mark it as accepted in
patchwork). So I'm fixing that oversight now.
- Ted
prev parent reply other threads:[~2011-05-25 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 10:13 [PATCH] e2fsprogs: fix freeing bitmap in allocation error path Lukas Czerner
2011-05-25 23:30 ` Ted 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=20110525233045.GF9520@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).