From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [PULL 0/9] Block layer patches
Date: Tue, 22 Oct 2024 18:48:54 +0200 [thread overview]
Message-ID: <20241022164903.282174-1-kwolf@redhat.com> (raw)
The following changes since commit 6f625ce2f21d6a1243065d236298277c56f972d5:
Merge tag 'pull-request-2024-10-21' of https://gitlab.com/thuth/qemu into staging (2024-10-21 17:12:59 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to 04bbc3ee52b32ac465547bb40c1f090a1b8f315a:
raw-format: Fix error message for invalid offset/size (2024-10-22 17:52:49 +0200)
----------------------------------------------------------------
Block layer patches
- Event throttling for BLOCK_IO_ERROR
- iotests: Fix backup-discard-source test for XFS
- Coverity fixes
- raw-format: Fix error message for invalid offset/size
----------------------------------------------------------------
Kevin Wolf (1):
raw-format: Fix error message for invalid offset/size
Leonid Kaplan (1):
block-backend: per-device throttling of BLOCK_IO_ERROR reports
Peter Maydell (4):
block/gluster: Use g_autofree for string in qemu_gluster_parse_json()
block/ssh.c: Don't double-check that characters are hex digits
tests/qemu-iotests/211.out: Update to expect MapEntry 'compressed' field
block/vdi.c: Make SECTOR_SIZE constant 64-bits
Vladimir Sementsov-Ogievskiy (3):
iotests/backup-discard-source: convert size variable to be int
iotests/backup-discard-source: don't use actual-size
qapi: add qom-path to BLOCK_IO_ERROR event
qapi/block-core.json | 9 ++++--
block/block-backend.c | 21 +++++++++++---
block/gluster.c | 7 ++---
block/raw-format.c | 4 +--
block/ssh.c | 12 ++++----
block/vdi.c | 4 +--
monitor/monitor.c | 7 +++--
tests/qemu-iotests/211.out | 6 ++--
tests/qemu-iotests/tests/backup-discard-source | 39 +++++++++++++++++---------
9 files changed, 70 insertions(+), 39 deletions(-)
next reply other threads:[~2024-10-22 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 16:48 Kevin Wolf [this message]
2024-10-22 16:48 ` [PULL 1/9] block/gluster: Use g_autofree for string in qemu_gluster_parse_json() Kevin Wolf
2024-10-22 16:48 ` [PULL 2/9] block/ssh.c: Don't double-check that characters are hex digits Kevin Wolf
2024-10-22 16:48 ` [PULL 3/9] tests/qemu-iotests/211.out: Update to expect MapEntry 'compressed' field Kevin Wolf
2024-10-22 16:48 ` [PULL 4/9] block/vdi.c: Make SECTOR_SIZE constant 64-bits Kevin Wolf
2024-10-22 16:48 ` [PULL 5/9] iotests/backup-discard-source: convert size variable to be int Kevin Wolf
2024-10-22 16:49 ` [PULL 6/9] iotests/backup-discard-source: don't use actual-size Kevin Wolf
2024-10-22 16:49 ` [PULL 7/9] qapi: add qom-path to BLOCK_IO_ERROR event Kevin Wolf
2024-10-22 16:49 ` [PULL 8/9] block-backend: per-device throttling of BLOCK_IO_ERROR reports Kevin Wolf
2024-10-22 16:49 ` [PULL 9/9] raw-format: Fix error message for invalid offset/size Kevin Wolf
2024-10-24 14:21 ` [PULL 0/9] Block layer patches Peter Maydell
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=20241022164903.282174-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).