From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>
Subject: Re: [PATCH] qom: use ERRP_GUARD in user_creatable_complete
Date: Fri, 19 Sep 2025 12:41:56 +0100 [thread overview]
Message-ID: <aM1BhOI4yE2SBNz_@redhat.com> (raw)
In-Reply-To: <87cy7m3cj9.fsf@pond.sub.org>
On Fri, Sep 19, 2025 at 01:30:18PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > With error_propagate, the stack trace from any error_abort/fatal
> > usage will start from the error_propagate() call, which is largely
> > useless. Using ERRP_GUARD ensures the stack trace starts from
> > the origin that reported the error.
>
> Yes.
>
> I've been chipping at error_propagate() uses on and off for a while.
> There are hundreds left.
Are there cases where it is still OK to use error_propagate or should
we be looking to eliminate all its usage ?
>
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-09-19 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 10:15 [PATCH] qom: use ERRP_GUARD in user_creatable_complete Daniel P. Berrangé
2025-09-19 10:33 ` Paolo Bonzini
2025-09-19 11:30 ` Markus Armbruster
2025-09-19 11:41 ` Daniel P. Berrangé [this message]
2025-09-19 12:06 ` Markus Armbruster
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=aM1BhOI4yE2SBNz_@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eduardo@habkost.net \
--cc=pbonzini@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 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.