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>
Subject: Re: [PATCH] multifd: Copy pages before compressing them with zlib
Date: Tue, 5 Jul 2022 16:27:07 +0100 [thread overview]
Message-ID: <YsRYS7PdeMohyUDi@work-vm> (raw)
In-Reply-To: <20220704164112.2890137-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().
Thanks for fixing that!
> [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://gitlab.com/qemu-project/qemu/-/issues/1099
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
>
> 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.
>
> migration/multifd-zlib.c | 35 ++++++++++++++++++++++-------------
> 1 file changed, 22 insertions(+), 13 deletions(-)
>
> diff --git a/migration/multifd-zlib.c b/migration/multifd-zlib.c
> index 3a7ae44485..b6b22b7d1f 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 */
> + uint8_t buf[];
> };
>
> /* Multifd zlib compression */
> @@ -43,9 +45,18 @@ struct zlib_data {
> */
> static int zlib_send_setup(MultiFDSendParams *p, Error **errp)
> {
> - struct zlib_data *z = g_new0(struct zlib_data, 1);
> - z_stream *zs = &z->zs;
> + /* This is the maximum size of the compressed buffer */
> + uint32_t zbuff_len = compressBound(MULTIFD_PACKET_SIZE);
> + size_t buf_len = qemu_target_page_size();
> + struct zlib_data *z;
> + z_stream *zs;
>
> + z = g_try_malloc0(sizeof(struct zlib_data) + buf_len + zbuff_len);
So I think this works; but wouldn't life be easier if you just used
separate malloc's for the buffers? You've got a lot of hairy pointer
maths below that would go away if they were separate.
Dave
> + if (!z) {
> + error_setg(errp, "multifd %u: out of memory for zlib_data", p->id);
> + return -1;
> + }
> + zs = &z->zs;
> zs->zalloc = Z_NULL;
> zs->zfree = Z_NULL;
> zs->opaque = Z_NULL;
> @@ -54,15 +65,8 @@ static int zlib_send_setup(MultiFDSendParams *p, Error **errp)
> error_setg(errp, "multifd %u: deflate init failed", p->id);
> return -1;
> }
> - /* 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;
> - }
> + z->zbuff_len = zbuff_len;
> + z->zbuff = z->buf + buf_len;
> p->data = z;
> return 0;
> }
> @@ -80,7 +84,6 @@ static void zlib_send_cleanup(MultiFDSendParams *p, Error **errp)
> struct zlib_data *z = p->data;
>
> deflateEnd(&z->zs);
> - g_free(z->zbuff);
> z->zbuff = NULL;
> g_free(p->data);
> p->data = NULL;
> @@ -114,8 +117,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
next prev parent reply other threads:[~2022-07-05 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 16:41 [PATCH] multifd: Copy pages before compressing them with zlib Ilya Leoshkevich
2022-07-04 16:51 ` Juan Quintela
2022-07-05 15:27 ` Dr. David Alan Gilbert [this message]
2022-07-05 17:22 ` Ilya Leoshkevich
2022-07-05 17:32 ` Dr. David Alan Gilbert
2022-07-05 16:00 ` Peter Maydell
2022-07-05 16:16 ` Dr. David Alan Gilbert
2022-07-05 16:27 ` Christian Borntraeger
2022-07-05 16:33 ` Dr. David Alan Gilbert
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 15:21 Ilya Leoshkevich
2022-03-30 14:35 ` Christian Borntraeger
2022-04-04 11:20 ` Dr. David Alan Gilbert
2022-04-04 12:09 ` Ilya Leoshkevich
2022-04-04 17:11 ` Dr. David Alan Gilbert
2022-04-04 12:45 ` Daniel P. Berrangé
2022-04-04 13:55 ` Juan Quintela
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=YsRYS7PdeMohyUDi@work-vm \
--to=dgilbert@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=iii@linux.ibm.com \
--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).