From: Mike Maslenkin <mike.maslenkin@gmail.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, den@virtuozzo.com,
stefanha@redhat.com, vsementsov@yandex-team.ru,
kwolf@redhat.com, hreitz@redhat.com
Subject: Re: [PATCH v2 01/20] parallels: Set s->used_bmap to NULL in parallels_free_used_bitmap()
Date: Sat, 21 Oct 2023 13:40:48 +0300 [thread overview]
Message-ID: <CAL77WPC79j7LUJNTYpf5uyH3JFViDKsMMRktzfgtoZKHUVhEWA@mail.gmail.com> (raw)
In-Reply-To: <20231019125854.390385-2-alexander.ivanov@virtuozzo.com>
On Thu, Oct 19, 2023 at 4:06 PM Alexander Ivanov
<alexander.ivanov@virtuozzo.com> wrote:
>
> After used bitmap freeng s->used_bmap points to the freed memory. If we try
> to free used bitmap one more time it leads to double free error.
>
> Set s->used_bmap to NULL to exclude double free error.
>
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
> ---
> block/parallels.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block/parallels.c b/block/parallels.c
> index 6b46623241..ba1fdde259 100644
> --- a/block/parallels.c
> +++ b/block/parallels.c
> @@ -244,6 +244,7 @@ static void parallels_free_used_bitmap(BlockDriverState *bs)
> {
> BDRVParallelsState *s = bs->opaque;
> s->used_bmap_size = 0;
> + s->used_bmap = NULL;
> g_free(s->used_bmap);
> }
Shouldn't it be added after g_free() call?
Regards,
Mike.
next prev parent reply other threads:[~2023-10-21 10:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 12:58 [PATCH v2 00/20] parallels: Add full dirty bitmap support Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 01/20] parallels: Set s->used_bmap to NULL in parallels_free_used_bitmap() Alexander Ivanov
2023-10-21 10:40 ` Mike Maslenkin [this message]
2023-10-24 10:29 ` Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 02/20] parallels: Move inactivation code to a separate function Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 03/20] parallels: Add mark_unused() helper Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 04/20] parallels: Move host clusters allocation to a separate function Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 05/20] parallels: Set data_end value in parallels_check_leak() Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 06/20] parallels: Recreate used bitmap " Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 07/20] parallels: Add a note about used bitmap in parallels_check_duplicate() Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 08/20] parallels: Create used bitmap even if checks needed Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 09/20] parallels: Make mark_used() and mark_unused() global functions Alexander Ivanov
2023-10-21 13:29 ` Mike Maslenkin
2023-10-24 10:31 ` Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 10/20] parallels: Add dirty bitmaps saving Alexander Ivanov
2023-10-21 10:40 ` Mike Maslenkin
2023-10-23 10:03 ` Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 11/20] parallels: Let image extensions work in RW mode Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 12/20] parallels: Handle L1 entries equal to one Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 13/20] parallels: Make a loaded dirty bitmap persistent Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 14/20] parallels: Reverse a conditional in parallels_check_leak() to reduce indents Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 15/20] parallels: Truncate images on the last used cluster Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 16/20] parallels: Check unused clusters in parallels_check_leak() Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 17/20] parallels: Remove unnecessary data_end field Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 18/20] tests: Add parallels images support to test 165 Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 19/20] tests: Turned on 256, 299, 304 and block-status-cache for parallels format Alexander Ivanov
2023-10-19 12:58 ` [PATCH v2 20/20] tests: Add parallels format support to image-fleecing Alexander Ivanov
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=CAL77WPC79j7LUJNTYpf5uyH3JFViDKsMMRktzfgtoZKHUVhEWA@mail.gmail.com \
--to=mike.maslenkin@gmail.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).