From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Cédric Le Goater" <clg@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org, farosas@suse.de, peter.maydell@linaro.org
Subject: Re: g_autoptr(Error)
Date: Wed, 26 Nov 2025 12:00:59 +0000 [thread overview]
Message-ID: <aSbr--ZbqzKVNDuC@redhat.com> (raw)
In-Reply-To: <87ecplc8yn.fsf@pond.sub.org>
On Wed, Nov 26, 2025 at 12:46:40PM +0100, Markus Armbruster wrote:
> Cédric Le Goater <clg@redhat.com> writes:
>
> > On 11/26/25 09:19, Cédric Le Goater wrote:
> >> On 11/25/25 17:15, Peter Xu wrote:
> >>> On Tue, Nov 25, 2025 at 12:46:01PM +0100, Markus Armbruster wrote:
>
> [...]
>
> On the review and merging of commit 18eb55546a5 (error: define
> g_autoptr() cleanup function for the Error type):
>
> >>>> I missed it. Not he submitter's fault; it was cc'ed to me.
> >>>
> >>> If someone to blame, it's the reviewer.
> >> At end, I was the one who merged this stuff. My bad.
> >>
> >> I felt confident at the time, as it was only a single-line change reviewed
> >> by a subsystem maintainer and the patch was large enough that this didn't
> >
> > s/patch/series/ makes more sense.
> >
> > Sorry for the noise.
>
> > C.
> >
> >
> >> raise my attention.
> >>
> >> But it should have been treated with greater caution, global features must
> >> be introduced together with concrete usage proposals. I think this would
> >> have raised some unconscious red flags.
> >> Thanks,
> >> C.
>
> Don't worry about it! From my point of view, the process worked okay.
> A big series got reviewed by maintainers, except for one little patch
> touching another subsystem, where that subsystem's maintainer (me)
> remained silent. The series was then merged without further delay.
>
> Would I have appreciate a timely nudge on that little patch? Sure. Is
> not nudging me a failure of sorts? Nope.
The other thing that plays in here is that we actively encourage use of
g_autoptr everywhere. It is very unusual for "Error" to be a type that
does NOT want g_autoptr, and thus the mistake is very much on the cards.
I've proposed it before myself & Markus caught it. I also caught one
other proposals to add it since my attempt. This third time it slipped
through review. I expect we'll see a 4th attempt to add it at some point.
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-11-26 12:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:05 [PATCH] migration: Fix double-free on error path Markus Armbruster
2025-11-25 7:11 ` Markus Armbruster
2025-11-25 15:41 ` Peter Xu
2025-11-25 7:12 ` Marc-André Lureau
2025-11-25 12:59 ` Markus Armbruster
2025-11-25 15:47 ` Peter Xu
2025-11-25 18:48 ` Markus Armbruster
2025-11-25 19:32 ` Peter Xu
2025-11-26 6:12 ` Should functions that free memory clear the pointer? (was: [PATCH] migration: Fix double-free on error path) Markus Armbruster
2025-11-26 8:21 ` Should functions that free memory clear the pointer? Cédric Le Goater
2025-11-25 7:16 ` [PATCH] migration: Fix double-free on error path Philippe Mathieu-Daudé
2025-11-25 7:40 ` g_autoptr(Error) (was: [PATCH] migration: Fix double-free on error path) Markus Armbruster
2025-11-25 11:25 ` Daniel P. Berrangé
2025-11-25 11:46 ` g_autoptr(Error) Markus Armbruster
2025-11-25 16:15 ` g_autoptr(Error) Peter Xu
2025-11-25 19:02 ` g_autoptr(Error) Markus Armbruster
2025-11-25 20:49 ` g_autoptr(Error) Peter Xu
2025-11-26 8:19 ` g_autoptr(Error) Cédric Le Goater
2025-11-26 10:26 ` g_autoptr(Error) Cédric Le Goater
2025-11-26 11:46 ` g_autoptr(Error) Markus Armbruster
2025-11-26 12:00 ` Daniel P. Berrangé [this message]
2025-11-26 12:41 ` g_autoptr(Error) Markus Armbruster
2025-11-26 13:27 ` g_autoptr(Error) Peter Maydell
2025-11-26 14:01 ` g_autoptr(Error) Markus Armbruster
2025-12-02 8:34 ` [PATCH] migration: Fix double-free on error path 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=aSbr--ZbqzKVNDuC@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=clg@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=peterx@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.