From: Max Reitz <mreitz@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/1] block: improve error handling in raw_open
Date: Fri, 23 Sep 2016 18:04:15 +0200 [thread overview]
Message-ID: <b81b4ba5-4058-33fe-cf0b-8889195a554c@redhat.com> (raw)
In-Reply-To: <20160908135905.86622-1-pasic@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
On 08.09.2016 15:59, 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. Do not have a patch for that, because I'm unsure
> whats the best way to deal with it. My guess right now is to make sure
> we propagate errors at least until reaching code which is called only
> QMP in context and handle communicating the error to the requester of
> the operation there. Any suggestions or ideas?
>
> The win32 part was not tested, and the sole reason I touched it is
> to not introduce unnecessary divergence.
>
> v3 -> v4:
> * rebased on current master
> v2 -> v3:
> * first save errno then error_setg_errno
> v1 -> v2:
> * fixed win32 by the correct error_setg_*
> * use the original errno consequently
> ---
> block/raw-posix.c | 1 +
> block/raw-win32.c | 1 +
> 2 files changed, 2 insertions(+)
Thank you, I've applied this patch to my block branch:
https://github.com/XanClic/qemu/commits/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 480 bytes --]
next prev parent reply other threads:[~2016-09-23 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 13:59 [Qemu-devel] [PATCH v4 1/1] block: improve error handling in raw_open Halil Pasic
2016-09-23 16:04 ` Max Reitz [this message]
2016-09-23 16:13 ` Max Reitz
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=b81b4ba5-4058-33fe-cf0b-8889195a554c@redhat.com \
--to=mreitz@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=pasic@linux.vnet.ibm.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).