From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paul Burton <pburton@wavecomp.com>,
qemu-devel@nongnu.org,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH-for-5.1 v3 5/7] hw/mips/boston: Add missing error-propagation code
Date: Wed, 29 Apr 2020 08:38:40 +0200 [thread overview]
Message-ID: <877dxyvlsf.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20200413205250.687-2-f4bug@amsat.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 13 Apr 2020 22:52:50 +0200")
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> Running the coccinelle script produced:
>
> $ spatch \
> --macro-file scripts/cocci-macro-file.h --include-headers \
> --sp-file scripts/coccinelle/find-missing-error_propagate.cocci \
> --keep-comments --smpl-spacing --dir .
> HANDLING: ./hw/mips/boston.c
> [[manual check required: error_propagate() might be missing in object_property_set_int() ./hw/mips/boston.c:462:4]]
> [[manual check required: error_propagate() might be missing in object_property_set_str() ./hw/mips/boston.c:460:4]]
>
> Since the uses are inside a MachineClass::init() function,
> directly use &error_fatal instead of error_propagate().
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> Reviewed-by: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
I duplicated this patch in
[PATCH 08/11] mips/boston: Fix boston_mach_init() error handling
[PATCH 09/11] mips/boston: Plug memory leak in boston_mach_init()
Sorry!
I'd replace my patches by yours to give you proper credit, but your
commit message mentions "the coccinelle script", presumably the one from
PATCH 3/7, and that patch isn't quite ready in my opinion. Also, only
my version documents the memory leak.
next prev parent reply other threads:[~2020-04-29 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 20:52 [PATCH-for-5.1 v3 4/7] migration/colo: Add missing error-propagation code Philippe Mathieu-Daudé
2020-04-13 20:52 ` [PATCH-for-5.1 v3 5/7] hw/mips/boston: " Philippe Mathieu-Daudé
2020-04-29 6:38 ` Markus Armbruster [this message]
2020-05-07 15:26 ` [PATCH-for-5.1 v3 4/7] migration/colo: " Dr. David Alan Gilbert
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=877dxyvlsf.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=pburton@wavecomp.com \
--cc=peter.maydell@linaro.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 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.