From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v3] multifd: Copy pages before compressing them with zlib
Date: Tue, 19 Jul 2022 12:37:30 +0100 [thread overview]
Message-ID: <YtaXenPX8gPYeWna@work-vm> (raw)
In-Reply-To: <20220705203559.2960949-1-iii@linux.ibm.com>
* Ilya Leoshkevich (iii@linux.ibm.com) wrote:
> zlib_send_prepare() compresses pages of a running VM. zlib does not
> make any thread-safety guarantees with respect to changing deflate()
> input concurrently with deflate() [1].
>
> One can observe problems due to this with the IBM zEnterprise Data
> Compression accelerator capable zlib [2]. When the hardware
> acceleration is enabled, migration/multifd/tcp/plain/zlib test fails
> intermittently [3] due to sliding window corruption. The accelerator's
> architecture explicitly discourages concurrent accesses [4]:
>
> Page 26-57, "Other Conditions":
>
> As observed by this CPU, other CPUs, and channel
> programs, references to the parameter block, first,
> second, and third operands may be multiple-access
> references, accesses to these storage locations are
> not necessarily block-concurrent, and the sequence
> of these accesses or references is undefined.
>
> Mark Adler pointed out that vanilla zlib performs double fetches under
> certain circumstances as well [5], therefore we need to copy data
> before passing it to deflate().
>
> [1] https://zlib.net/manual.html
> [2] https://github.com/madler/zlib/pull/410
> [3] https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg03988.html
> [4] http://publibfp.dhe.ibm.com/epubs/pdf/a227832c.pdf
> [5] https://lists.gnu.org/archive/html/qemu-devel/2022-07/msg00889.html
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Queued, thank you!
Dave
> ---
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg06841.html
> v1 -> v2: Rebase, mention Mark Adler's reply in the commit message.
>
> v2: https://lists.gnu.org/archive/html/qemu-devel/2022-07/msg00627.html
> v2 -> v3: Get rid of pointer maths (David).
> Use a more relevant link to Mark Adler's comment (Peter).
>
> migration/multifd-zlib.c | 38 ++++++++++++++++++++++++++++++--------
> 1 file changed, 30 insertions(+), 8 deletions(-)
>
> diff --git a/migration/multifd-zlib.c b/migration/multifd-zlib.c
> index 3a7ae44485..18213a9513 100644
> --- a/migration/multifd-zlib.c
> +++ b/migration/multifd-zlib.c
> @@ -27,6 +27,8 @@ struct zlib_data {
> uint8_t *zbuff;
> /* size of compressed buffer */
> uint32_t zbuff_len;
> + /* uncompressed buffer of size qemu_target_page_size() */
> + uint8_t *buf;
> };
>
> /* Multifd zlib compression */
> @@ -45,26 +47,38 @@ static int zlib_send_setup(MultiFDSendParams *p, Error **errp)
> {
> struct zlib_data *z = g_new0(struct zlib_data, 1);
> z_stream *zs = &z->zs;
> + const char *err_msg;
>
> zs->zalloc = Z_NULL;
> zs->zfree = Z_NULL;
> zs->opaque = Z_NULL;
> if (deflateInit(zs, migrate_multifd_zlib_level()) != Z_OK) {
> - g_free(z);
> - error_setg(errp, "multifd %u: deflate init failed", p->id);
> - return -1;
> + err_msg = "deflate init failed";
> + goto err_free_z;
> }
> /* This is the maxium size of the compressed buffer */
> z->zbuff_len = compressBound(MULTIFD_PACKET_SIZE);
> z->zbuff = g_try_malloc(z->zbuff_len);
> if (!z->zbuff) {
> - deflateEnd(&z->zs);
> - g_free(z);
> - error_setg(errp, "multifd %u: out of memory for zbuff", p->id);
> - return -1;
> + err_msg = "out of memory for zbuff";
> + goto err_deflate_end;
> + }
> + z->buf = g_try_malloc(qemu_target_page_size());
> + if (!z->buf) {
> + err_msg = "out of memory for buf";
> + goto err_free_zbuff;
> }
> p->data = z;
> return 0;
> +
> +err_free_zbuff:
> + g_free(z->zbuff);
> +err_deflate_end:
> + deflateEnd(&z->zs);
> +err_free_z:
> + g_free(z);
> + error_setg(errp, "multifd %u: %s", p->id, err_msg);
> + return -1;
> }
>
> /**
> @@ -82,6 +96,8 @@ static void zlib_send_cleanup(MultiFDSendParams *p, Error **errp)
> deflateEnd(&z->zs);
> g_free(z->zbuff);
> z->zbuff = NULL;
> + g_free(z->buf);
> + z->buf = NULL;
> g_free(p->data);
> p->data = NULL;
> }
> @@ -114,8 +130,14 @@ static int zlib_send_prepare(MultiFDSendParams *p, Error **errp)
> flush = Z_SYNC_FLUSH;
> }
>
> + /*
> + * Since the VM might be running, the page may be changing concurrently
> + * with compression. zlib does not guarantee that this is safe,
> + * therefore copy the page before calling deflate().
> + */
> + memcpy(z->buf, p->pages->block->host + p->normal[i], page_size);
> zs->avail_in = page_size;
> - zs->next_in = p->pages->block->host + p->normal[i];
> + zs->next_in = z->buf;
>
> zs->avail_out = available;
> zs->next_out = z->zbuff + out_size;
> --
> 2.35.3
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2022-07-19 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 20:35 [PATCH v3] multifd: Copy pages before compressing them with zlib Ilya Leoshkevich
2022-07-13 15:35 ` Dr. David Alan Gilbert
2022-07-19 11:37 ` Dr. David Alan Gilbert [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=YtaXenPX8gPYeWna@work-vm \
--to=dgilbert@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=iii@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).