From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, den@openvz.org,
Thomas Huth <thuth@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PULL v2 0/9] parallels: fix reachable assertion and related bounds-checking gaps
Date: Wed, 29 Jul 2026 06:13:22 -0400 [thread overview]
Message-ID: <20260729101322.GA1365083@fedora> (raw)
In-Reply-To: <20260728153849.601939-1-den@openvz.org>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/11.1 for any user-visible changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-29 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 15:38 [PULL v2 0/9] parallels: fix reachable assertion and related bounds-checking gaps Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 1/9] parallels: fix integer overflow in header size calculation Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 2/9] parallels: read header/BAT table in bounded chunks Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 3/9] parallels: fix bat_entries overflow in image creation Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 4/9] parallels: reject BAT entries pointing outside backed storage Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 5/9] parallels: validate bitmap L1 table size before allocating it Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 6/9] parallels: skip loading a genuinely empty bitmap L1 table Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 7/9] parallels: avoid fatal abort on large " Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 8/9] parallels: validate BAT capacity against advertised disk size Denis V. Lunev
2026-07-28 15:38 ` [PULL v2 9/9] MAINTAINERS: update parallels tree location Denis V. Lunev
2026-07-29 10:13 ` Stefan Hajnoczi [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=20260729101322.GA1365083@fedora \
--to=stefanha@redhat.com \
--cc=den@openvz.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.