From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v5 1/1] block: improve error handling in raw_open
Date: Fri, 14 Oct 2016 18:27:59 +0200 [thread overview]
Message-ID: <3d9f0297-47a4-d782-ecba-70542ce8548e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161014155919.GI3482@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
On 10/14/2016 05:59 PM, Stefan Hajnoczi wrote:
> On Tue, Oct 11, 2016 at 04:12:35PM +0200, Halil Pasic wrote:
>> > Make raw_open for POSIX more consistent in handling errors by setting
>> > the error object also when qemu_open fails. The error object was set
>> > generally set in case of errors, but I guess this case was overlooked.
>> > Do the same for win32.
>> >
>> > Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
>> > Reviewed-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
>> > Tested-by: Marc Hartmayer <mhartmay@linux.vnet.ibm.com> (POSIX only)
>> >
>> > ---
>> >
>> > Stumbled upon this (POSIX) while testing VMs with too many SCSI disks in
>> > respect to my nofile limit. When open hits the nofile limit while trying
>> > to hotplug yet another SCSI disk via libvirt we end up with no adequate
>> > error message (one stating too many files). Sadly this patch in not
>> > sufficient to fix this problem because drive_new (/qemu/blockdev.c)
>> > handles errors using error_report_err which is documented as not to be
>> > used in QMP context.
>> >
>> > The win32 part was not tested, and the sole reason I touched it is
>> > to not introduce unnecessary divergence.
>> >
>> > v4 -> v5:
>> > * fix qemu-iotests by adding the filename to the message
> This patch doesn't modify any iotests golden master files. Does this
> mean the iotests output is unchanged?
>
Exactly. Instead of modifying the golden masters I choose to modify
the message generated by me and make it more verbose by appending
the filename in question.
Thanks for the review!
Halil
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-10-14 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:12 [Qemu-devel] [PATCH v5 1/1] block: improve error handling in raw_open Halil Pasic
2016-10-14 15:59 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-10-14 16:27 ` Halil Pasic [this message]
2016-10-17 10:19 ` Kevin Wolf
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=3d9f0297-47a4-d782-ecba-70542ce8548e@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).