From: Markus Armbruster <armbru@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Honglei Huang <honghuan@amd.com>,
alex.bennee@linaro.org, dmitry.osipenko@collabora.com,
odaki@rsg.ci.i.u-tokyo.ac.jp, mst@redhat.com,
cohuck@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
Ray.Huang@amd.com, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [v6 0/2] virtio-gpu: fix error handling and improve consistency
Date: Fri, 06 Feb 2026 08:05:41 +0100 [thread overview]
Message-ID: <874inuxsfu.fsf@pond.sub.org> (raw)
In-Reply-To: <39541134-0c64-439c-b270-22e59dcbe994@tls.msk.ru> (Michael Tokarev's message of "Fri, 6 Feb 2026 01:07:07 +0300")
Michael Tokarev <mjt@tls.msk.ru> writes:
> On 1/13/26 04:52, Honglei Huang wrote:
>> This series addresses error handling issues in virtio-gpu and improves
>> code consistency across the virtio-gpu subsystem.
>> The first patch fixes a critical bug in virgl_cmd_resource_create_blob()
>> where an inverted error check causes the function to fail when it should
>> succeed. This is a standalone bug fix that should be backported.
>> The second patch improves code consistency by unifying the error checking
>> style for virtio_gpu_create_mapping_iov() in if-statement contexts across
>> virtio-gpu files, following the preferred QEMU coding convention.
>> Changes since v5:
>> - Reverted changes to virtio-gpu-rutabaga.c to keep CHECK macro usage
>> consistent with other error checks in the same file
>> - Updated patch 2 commit message to clarify that CHECK macro patterns
>> in rutabaga.c are intentionally left unchanged
>> Changes since v4:
>> - Split the single patch into two separate patches for better clarity
>> - Separated the critical bug fix from the style consistency improvements
>> - The bug fix (patch 1) can now be easily identified and backported
>> - The consistency improvements (patch 2) are clearly marked as cleanup
>> Changes since v3:
>> - Extended consistency improvements to virtio-gpu-rutabaga.c
>> - Changed CHECK(!ret) to CHECK(ret >= 0) and CHECK(!result) to
>> CHECK(result >= 0) in rutabaga functions for consistency
>> - Now covers all virtio-gpu files that use virtio_gpu_create_mapping_iov()
>> Changes since v2:
>> - Use 'if (ret < 0)' instead of 'if (ret != 0)' following maintainer's
>> feedback on preferred QEMU coding style for error checking functions
>> that return 0 on success and negative on error
>> - Updated all similar usages across virtio-gpu files for consistency
>> - Expanded scope from single function fix to codebase-wide style consistency
>> Honglei Huang (2):
>> virtio-gpu: fix error handling in virgl_cmd_resource_create_blob
>> virtio-gpu: use consistent error checking for
>> virtio_gpu_create_mapping_iov
>> hw/display/virtio-gpu-virgl.c | 4 ++--
>> hw/display/virtio-gpu.c | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
> Is this a qemu-stable material? I'm a bit confused here. The first
> patch looks like it is, the second I can't decide.
>
> Please let me know if I should pick this up for qemu-stable or not.
> For now I'm picking up the first change.
I think that's fine.
next prev parent reply other threads:[~2026-02-06 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 1:52 [v6 0/2] virtio-gpu: fix error handling and improve consistency Honglei Huang
2026-01-13 1:52 ` [v6 1/2] virtio-gpu: fix error handling in virgl_cmd_resource_create_blob Honglei Huang
2026-01-13 1:52 ` [v6 2/2] virtio-gpu: use consistent error checking for virtio_gpu_create_mapping_iov Honglei Huang
2026-02-05 22:07 ` [v6 0/2] virtio-gpu: fix error handling and improve consistency Michael Tokarev
2026-02-06 7:05 ` Markus Armbruster [this message]
2026-03-03 11:05 ` Alex Bennée
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 2:02 Honglei Huang
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=874inuxsfu.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=Ray.Huang@amd.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=honghuan@amd.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.