From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: marcel@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] aml-build: don't modify child
Date: Mon, 9 Mar 2015 10:27:15 +0100 [thread overview]
Message-ID: <20150309102715.706fbd6f@nial.brq.redhat.com> (raw)
In-Reply-To: <1425757887-4819-1-git-send-email-mst@redhat.com>
On Sat, 7 Mar 2015 20:51:33 +0100
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> this code:
> aml_append(foo, bar);
>
> might, non-intuitively, modify bar, which means that e.g. the following
> might not DTRT:
>
> c = ....;
> aml_append(a, c);
> aml_append(b, c);
>
> to fix, simply allocate an intermediate array,
> and always modify that.
While at it, could 'c' be made 'const Aml*' argument of aml_append() ???
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> hw/acpi/aml-build.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
> index 876cada..ff12b28 100644
> --- a/hw/acpi/aml-build.c
> +++ b/hw/acpi/aml-build.c
> @@ -335,26 +335,29 @@ static void build_buffer(GArray *array, uint8_t op)
>
> void aml_append(Aml *parent_ctx, Aml *child)
> {
> + GArray *buf = build_alloc_array();
> + build_append_array(buf, child->buf);
> +
> switch (child->block_flags) {
> case AML_OPCODE:
> build_append_byte(parent_ctx->buf, child->op);
> break;
> case AML_EXT_PACKAGE:
> - build_extop_package(child->buf, child->op);
> + build_extop_package(buf, child->op);
> break;
> case AML_PACKAGE:
> - build_package(child->buf, child->op);
> + build_package(buf, child->op);
> break;
> case AML_RES_TEMPLATE:
> - build_append_byte(child->buf, 0x79); /* EndTag */
> + build_append_byte(buf, 0x79); /* EndTag */
> /*
> * checksum operations are treated as succeeded if checksum
> * field is zero. [ACPI Spec 1.0b, 6.4.2.8 End Tag]
> */
> - build_append_byte(child->buf, 0);
> + build_append_byte(buf, 0);
> /* fall through, to pack resources in buffer */
> case AML_BUFFER:
> - build_buffer(child->buf, child->op);
> + build_buffer(buf, child->op);
> break;
> case AML_NO_OPCODE:
> break;
> @@ -362,7 +365,8 @@ void aml_append(Aml *parent_ctx, Aml *child)
> assert(0);
> break;
> }
> - build_append_array(parent_ctx->buf, child->buf);
> + build_append_array(parent_ctx->buf, buf);
> + build_free_array(buf);
> }
>
> /* ACPI 1.0b: 16.2.5.1 Namespace Modifier Objects Encoding: DefScope */
next prev parent reply other threads:[~2015-03-09 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 19:51 [Qemu-devel] [PATCH] aml-build: don't modify child Michael S. Tsirkin
2015-03-09 9:27 ` Igor Mammedov [this message]
2015-03-09 9:30 ` Michael S. Tsirkin
2015-03-09 9:36 ` Igor Mammedov
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=20150309102715.706fbd6f@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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).