Re: [Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

Reviewed-by: liguang lig.f...@cn.fujitsu.com 在 2013-06-03一的 18:23 +0200，Igor Mammedov写道： spotted by Coverity, x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing x86_reg_info_32[CPU_NB_REGS32] will be one element off array. Yes, it will. Signed-off-by: Igor Mammedov

Re: [Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

Am 03.06.2013 18:23, schrieb Igor Mammedov: spotted by Coverity, x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing x86_reg_info_32[CPU_NB_REGS32] will be one element off array. Signed-off-by: Igor Mammedov imamm...@redhat.com --- target-i386/cpu.c |2 +- 1 files changed,

[Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

spotted by Coverity, x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing x86_reg_info_32[CPU_NB_REGS32] will be one element off array. Signed-off-by: Igor Mammedov imamm...@redhat.com --- target-i386/cpu.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

Re: [Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

On 06/03/2013 11:23 AM, Igor Mammedov wrote: spotted by Coverity, x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing x86_reg_info_32[CPU_NB_REGS32] will be one element off array. Signed-off-by: Igor Mammedov imamm...@redhat.com --- target-i386/cpu.c |2 +- 1 files