qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Prívozník" <mprivozn@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] chardev: Propagate error from logfile opening
Date: Mon, 6 Sep 2021 14:07:40 +0200	[thread overview]
Message-ID: <d9a28588-0aa0-92f7-e147-58dd8e913576@redhat.com> (raw)
In-Reply-To: <CAMxuvayipXmaR5qWgFEbJpwnHj-pzOx0z3mR1JBLRc_KqqJvtg@mail.gmail.com>

On 8/17/21 11:54 AM, Marc-André Lureau wrote:
> On Tue, Aug 17, 2021 at 12:56 PM Michal Privoznik <mprivozn@redhat.com>
> wrote:
> 
>> If a chardev has a logfile the file is opened using
>> qemu_open_old() which does the job, but since @errp is not
>> propagated into qemu_open_internal() we lose much more accurate
>> error and just report "Unable to open logfile $errno".  When
>> using plain files, it's probably okay as nothing complex is
>> happening behind the curtains. But the problem becomes more
>> prominent when passing an "/dev/fdset/XXX" path since much more
>> needs to be done.
>>
>> The fix is to use qemu_create() which passes @errp further down.
>>
>> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>>
> 
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>

Thanks, can you add it to your pull queue please?

Michal



  reply	other threads:[~2021-09-06 12:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  8:56 [PATCH 0/2] Two chardev with fdset fixes Michal Privoznik
2021-08-17  8:56 ` [PATCH 1/2] chardev: Propagate error from logfile opening Michal Privoznik
2021-08-17  9:12   ` Philippe Mathieu-Daudé
2021-08-17  9:54   ` Marc-André Lureau
2021-09-06 12:07     ` Michal Prívozník [this message]
2021-08-17  8:56 ` [PATCH 2/2] monitor: Report EBADFD if fdset contains invalid FD Michal Privoznik
2021-08-17  9:59   ` Marc-André Lureau
2021-08-17 11:46     ` Michal Prívozník
2021-08-18  8:39     ` Daniel P. Berrangé

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=d9a28588-0aa0-92f7-e147-58dd8e913576@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --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).