From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-trivial@nongnu.org,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: [PATCH] block: Remove trailing newline in format used by error_report API
Date: Mon, 8 Jun 2020 08:14:44 +0200 [thread overview]
Message-ID: <b4251bb2-bd76-01f0-26e2-563ab4ec7631@redhat.com> (raw)
In-Reply-To: <874krmyxlt.fsf@dusky.pond.sub.org>
On 6/8/20 6:45 AM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>
>> On 2/28/20 6:32 PM, Markus Armbruster wrote:
[...]
>>> warn_reportf_err() is a convenience function to error_prepend(),
>>> warn_report() and free @local_err.
> [...]
>> Why warn_reportf_err() doesn't take a 'Error **err' instead, to set err
>> to NULL after freeing *err?
>
> Why doesn't free() take a void ** argument, to set the pointer to null
> after freeing what it points to? Why doesn't close() take an int *
> argument?
=)
Usually I see the code checking an Error* hasn't been set by a callee.
If it has, the caller usually returns.
You explained me warn_reportf_err() consume Error* and free() it.
So regarding the rest of our Error* use, a function calling
warn_reportf_err has to do extra care to set Error* to NULL.
Genuinely looks confuse or dangerous to me...
Note however I was not asking for a change, just asking 'why'
to better understand if there were not a design problem, or
o invalid use of different APIs.
>
> [...]
>
prev parent reply other threads:[~2020-06-08 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 12:36 [PATCH] block: Remove trailing newline in format used by error_report API Philippe Mathieu-Daudé
2020-02-28 13:16 ` Liam Merwick
2020-02-28 17:32 ` Markus Armbruster
2020-06-05 14:26 ` Philippe Mathieu-Daudé
2020-06-08 4:45 ` Markus Armbruster
2020-06-08 6:14 ` Philippe Mathieu-Daudé [this message]
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=b4251bb2-bd76-01f0-26e2-563ab4ec7631@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).