From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: peter.maydell@linaro.org,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
claudio.fontana@huawei.com, qemu-devel@nongnu.org,
rth@twiddle.net, afaerber@suse.de, egdar.iglesias@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3 6/7] disas: cris: Fix 0 buffer length case
Date: Fri, 29 May 2015 15:21:15 +1000 [thread overview]
Message-ID: <20150529052115.GH17116@toto> (raw)
In-Reply-To: <0279412b5ad90c5aa113c349941b319b28672f1b.1432506704.git.crosthwaite.peter@gmail.com>
On Sun, May 24, 2015 at 03:47:19PM -0700, Peter Crosthwaite wrote:
> Cris has the complication of variable length instructions and has
> a check in place to clamp memory reads in case the disas request
> doesn't have enough bytes for the instruction being disas'd. This
> breaks down in the case where disassembling for the monitor where
> the buffer length is defaulted to 0.
>
> The buffer length should never be zero for a regular target_disas,
> so we can safely assume the 0 case is for the monitor in which case
> consider the buffer length to be the max for cris instructions.
>
> Signed-off-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> disas/cris.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/disas/cris.c b/disas/cris.c
> index e6cff7a..1b76a09 100644
> --- a/disas/cris.c
> +++ b/disas/cris.c
> @@ -2575,9 +2575,9 @@ print_insn_cris_generic (bfd_vma memaddr,
> If we can't get any data, or we do not get enough data, we print
> the error message. */
>
> - nbytes = info->buffer_length;
> - if (nbytes > MAX_BYTES_PER_CRIS_INSN)
> - nbytes = MAX_BYTES_PER_CRIS_INSN;
> + nbytes = info->buffer_length ? info->buffer_length
> + : MAX_BYTES_PER_CRIS_INSN;
> + nbytes = MIN(nbytes, MAX_BYTES_PER_CRIS_INSN);
> status = (*info->read_memory_func) (memaddr, buffer, nbytes, info);
>
> /* If we did not get all we asked for, then clear the rest.
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-05-29 5:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 22:47 [Qemu-devel] [PATCH v3 0/7] Unify and QOMify (target|monitor)_disas Peter Crosthwaite
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 1/7] disas: Add print_insn to disassemble info Peter Crosthwaite
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 2/7] disas: QOMify target specific setup Peter Crosthwaite
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 3/7] disas: arm-a64: Make printfer and stream variable Peter Crosthwaite
2015-06-24 3:32 ` Peter Crosthwaite
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 4/7] disas: arm: QOMify target specific disas setup Peter Crosthwaite
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 5/7] disas: microblaze: " Peter Crosthwaite
2015-05-29 4:43 ` Peter Crosthwaite
2015-05-29 4:45 ` Edgar E. Iglesias
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 6/7] disas: cris: Fix 0 buffer length case Peter Crosthwaite
2015-05-29 5:21 ` Edgar E. Iglesias [this message]
2015-05-24 22:47 ` [Qemu-devel] [PATCH v3 7/7] disas: cris: QOMify target specific disas setup Peter Crosthwaite
2015-05-29 5:22 ` Edgar E. Iglesias
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=20150529052115.GH17116@toto \
--to=edgar.iglesias@gmail.com \
--cc=afaerber@suse.de \
--cc=claudio.fontana@huawei.com \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=egdar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).