exec/memory: Enforce checking MemTxResult values
v2 cover exec/memory: Enforce checking MemTxResult values
Various places ignore the MemTxResult indicator of transaction failed. Fix the easy places. The rest are the DMA devices, which require deeper analysis.
Since v1:
- Dropped "exec/memory: Emit warning when MemTxResult is ignored"
https://www.mail-archive.com/[email protected]/msg704180.html
Philippe Mathieu-Daudé (7):
exec: Let address_space_read/write_cached() propagate MemTxResult
exec: Propagate cpu_memory_rw_debug() error
disas: Let disas::read_memory() handler return EIO on error hw/elf_ops: Do not ignore write failures when loading ELF hw/arm/boot: Abort if set_kernel_args() fails accel/kvm: Let KVM_EXIT_MMIO return error hw/core/loader: Assert loading ROM regions succeeds at reset
include/exec/cpu-all.h | 1 + include/exec/memory.h | 19 +++++++++++-------- include/hw/elf_ops.h | 11 ++++++++--- accel/kvm/kvm-all.c | 13 +++++++------ disas.c | 13 ++++++++----- exec.c | 28 ++++++++++++++++------------ hw/arm/boot.c | 19 +++++++++++++------ hw/core/loader.c | 8 ++++++-- 8 files changed, 70 insertions(+), 42 deletions(-)
Signature · 1 line
2.21.3
PATCH v2 1/7 exec: Let address_space_read/write_cached() propagate MemTxResult
Both address_space_read_cached_slow() and address_space_write_cached_slow() return a MemTxResult type. Do not discard it, return it to the caller.
--- include/exec/memory.h | 19 +++++++++++-------- exec.c | 16 ++++++++-------- 2 files changed, 19 insertions(+), 16 deletions(-)
include/exec/memory.h +11 -8
@@ -2343,10 +2343,11 @@ void *qemu_map_ram_ptr(RAMBlock *ram_block, ram_addr_t addr);/* Internal functions, part of the implementation of address_space_read_cached * and address_space_write_cached. */ -void address_space_read_cached_slow (MemoryRegionCache *cache, -hwaddr addr,void *buf,hwaddr len); -void address_space_write_cached_slow (MemoryRegionCache *cache, -hwaddr addr,const void *buf,hwaddr len); +MemTxResult address_space_read_cached_slow (MemoryRegionCache *cache, +hwaddr addr,void *buf,hwaddr len); +MemTxResult address_space_write_cached_slow (MemoryRegionCache *cache, +hwaddr addr,const void *buf, +hwaddr len);static inline bool memory_access_is_direct (MemoryRegion *mr,bool is_write) {
@@ -2411,15 +2412,16 @@ MemTxResult address_space_read(AddressSpace *as, hwaddr addr,* @buf: buffer with the data transferred * @len: length of the data transferred */ -static inline void +static inline MemTxResult address_space_read_cached (MemoryRegionCache *cache,hwaddr addr,void *buf,hwaddr len) {assert (addr < cache->len && len <= cache->len - addr);if (likely (cache->ptr)) {memcpy (buf, cache->ptr + addr, len); +return MEMTX_OK ; }else { -address_space_read_cached_slow (cache, addr, buf, len); +return address_space_read_cached_slow (cache, addr, buf, len); } }
@@ -2431,15 +2433,16 @@ address_space_read_cached(MemoryRegionCache *cache, hwaddr addr,* @buf: buffer with the data transferred * @len: length of the data transferred */ -static inline void +static inline MemTxResult address_space_write_cached (MemoryRegionCache *cache,hwaddr addr,const void *buf,hwaddr len) {assert (addr < cache->len && len <= cache->len - addr);if (likely (cache->ptr)) {memcpy (cache->ptr + addr, buf, len); +return MEMTX_OK ; }else { -address_space_write_cached_slow (cache, addr, buf, len); +return address_space_write_cached_slow (cache, addr, buf, len); } }
exec.c +8 -8
@@ -3716,7 +3716,7 @@ static inline MemoryRegion *address_space_translate_cached(/* Called from RCU critical section. address_space_read_cached uses this * out of line function when the target is an MMIO or IOMMU region. */ -void +MemTxResult address_space_read_cached_slow (MemoryRegionCache *cache,hwaddr addr,void *buf,hwaddr len) {
@@ -3726,15 +3726,15 @@ address_space_read_cached_slow(MemoryRegionCache *cache, hwaddr addr, l = len; mr =address_space_translate_cached (cache, addr, &addr1, &l, false,MEMTXATTRS_UNSPECIFIED ); -flatview_read_continue (cache->fv, - addr,MEMTXATTRS_UNSPECIFIED , buf, len, - addr1, l, mr); +return flatview_read_continue (cache->fv, + addr,MEMTXATTRS_UNSPECIFIED , buf, len, + addr1, l, mr); }/* Called from RCU critical section. address_space_write_cached uses this * out of line function when the target is an MMIO or IOMMU region. */ -void +MemTxResult address_space_write_cached_slow (MemoryRegionCache *cache,hwaddr addr,const void *buf,hwaddr len) {
@@ -3744,9 +3744,9 @@ address_space_write_cached_slow(MemoryRegionCache *cache, hwaddr addr, l = len; mr =address_space_translate_cached (cache, addr, &addr1, &l, true,MEMTXATTRS_UNSPECIFIED ); -flatview_write_continue (cache->fv, - addr,MEMTXATTRS_UNSPECIFIED , buf, len, - addr1, l, mr); +return flatview_write_continue (cache->fv, + addr,MEMTXATTRS_UNSPECIFIED , buf, len, + addr1, l, mr); }#define ARG1_DECL MemoryRegionCache *cache
Signature · 1 line
2.21.3
Re: [PATCH v2 1/7] exec: Let address_space_read/write_cached() propagate MemTxResult
Quoted 10 lines · Philippe Mathieu-Daudé
Both
address_space_read_cached_slow()andaddress_space_write_cached_slow()return a MemTxResult type. Do not discard it, return it to the caller.Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- include/exec/memory.h | 19 +++++++++++-------- exec.c | 16 ++++++++-------- 2 files changed, 19 insertions(+), 16 deletions(-)
thanks
-- PMM
PATCH v2 2/7 exec: Propagate cpu_memory_rw_debug() error
In reply to Philippe Mathieu-DaudéDo not ignore the MemTxResult error type returned by the address_space_rw() API.
--- include/exec/cpu-all.h | 1 + exec.c | 12 ++++++++---- 2 files changed, 9 insertions(+), 4 deletions(-)
include/exec/cpu-all.h +1 -0
@@ -413,6 +413,7 @@ void dump_exec_info(void);void dump_opcount_info (void );#endif /* !CONFIG_USER_ONLY */ +/* Returns: 0 on success, -1 on error */ int cpu_memory_rw_debug (CPUState *cpu,target_ulong addr,void *ptr,target_ulong len,bool is_write);
exec.c +8 -4
@@ -3769,6 +3769,7 @@ int cpu_memory_rw_debug(CPUState *cpu, target_ulong addr,while (len >0 ) {int asidx;MemTxAttrs attrs; +MemTxResult res; page = addr &TARGET_PAGE_MASK ; phys_addr =cpu_get_phys_page_attrs_debug (cpu, page, &attrs);
@@ -3781,11 +3782,14 @@ int cpu_memory_rw_debug(CPUState *cpu, target_ulong addr, l = len; phys_addr += (addr & ~TARGET_PAGE_MASK );if (is_write) { -address_space_write_rom (cpu->cpu_ases[asidx].as, phys_addr, - attrs, buf, l); + res =address_space_write_rom (cpu->cpu_ases[asidx].as, phys_addr, + attrs, buf, l); }else { -address_space_read (cpu->cpu_ases[asidx].as, phys_addr, attrs, buf, - l); + res =address_space_read (cpu->cpu_ases[asidx].as, phys_addr, + attrs, buf, l); + } +if (res !=MEMTX_OK ) { +return -1 ; } len -= l; buf += l;
Signature · 1 line
2.21.3
PATCH v2 3/7 disas: Let disas::read_memory() handler return EIO on error
In reply to Philippe Mathieu-DaudéBoth cpu_memory_rw_debug() and address_space_read() return an error on failed transaction. Check the returned value, and return EIO in case of error.
--- disas.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
disas.c +8 -5
@@ -39,9 +39,11 @@ target_read_memory (bfd_vma memaddr, struct disassemble_info *info) {CPUDebug *s =container_of (info, CPUDebug, info); +int r; -cpu_memory_rw_debug (s->cpu, memaddr, myaddr, length,0 ); -return 0 ; + r =cpu_memory_rw_debug (s->cpu, memaddr, myaddr, length,0 ); + +return r ?EIO :0 ; }/* Print an error message. We can assume that this is in response to
@@ -718,10 +720,11 @@ physical_read_memory(bfd_vma memaddr, bfd_byte *myaddr, int length, struct disassemble_info *info) {CPUDebug *s =container_of (info, CPUDebug, info); +MemTxResult res; -address_space_read (s->cpu->as, memaddr,MEMTXATTRS_UNSPECIFIED , - myaddr, length); -return 0 ; + res =address_space_read (s->cpu->as, memaddr,MEMTXATTRS_UNSPECIFIED , + myaddr, length); +return res ==MEMTX_OK ?0 :EIO ; }/* Disassembler for the monitor. */
Signature · 1 line
2.21.3
PATCH v2 4/7 hw/elf_ops: Do not ignore write failures when loading ELF
In reply to Philippe Mathieu-DaudéDo not ignore the MemTxResult error type returned by address_space_write().
--- include/hw/elf_ops.h | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
include/hw/elf_ops.h +8 -3
@@ -553,9 +553,14 @@ static int glue(load_elf, SZ)(const char *name, int fd,rom_add_elf_program (label, mapped_file, data, file_size, mem_size, addr, as); }else { -address_space_write (as ? as : &address_space_memory, - addr,MEMTXATTRS_UNSPECIFIED , - data, file_size); +MemTxResult res; + + res =address_space_write (as ? as : &address_space_memory, + addr,MEMTXATTRS_UNSPECIFIED , + data, file_size); +if (res !=MEMTX_OK ) { + goto fail; + } } }
Signature · 1 line
2.21.3
Re: [PATCH v2 4/7] hw/elf_ops: Do not ignore write failures when loading ELF
Quoted 7 lines · Philippe Mathieu-Daudé
Do not ignore the MemTxResult error type returned by
address_space_write().Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- include/hw/elf_ops.h | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
Quoted 26 lines
include/hw/elf_ops.h +8
-3@@ -553,9 +553,14 @@ static int glue(load_elf, SZ)(const char *name, int fd,rom_add_elf_program (label, mapped_file, data, file_size, mem_size, addr, as); }else { -address_space_write (as ? as : &address_space_memory, - addr,MEMTXATTRS_UNSPECIFIED , - data, file_size); +MemTxResult res; + + res =address_space_write (as ? as : &address_space_memory, + addr,MEMTXATTRS_UNSPECIFIED , + data, file_size); +if (res !=MEMTX_OK ) { + goto fail; + } } }Signature · 1 line
2.21.3
PATCH v2 5/7 hw/arm/boot: Abort if set_kernel_args() fails
In reply to Philippe Mathieu-DaudéIf a address_space_write() fails while callingset_kernel_args(), the guest kernel will boot
using crap data. Avoid that by aborting if this
ever occurs.
--- hw/arm/boot.c | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-)
hw/arm/boot.c +13 -6
@@ -291,7 +291,8 @@ static inline bool have_dtb(const struct arm_boot_info *info)#define WRITE_WORD (p, value) do { \ address_space_stl_notdirty(as, p, value, \ - MEMTXATTRS_UNSPECIFIED, NULL); \ + MEMTXATTRS_UNSPECIFIED, &result); \ + assert(result == MEMTX_OK); \ p += 4; \ } while (0)
@@ -300,6 +301,7 @@ static void set_kernel_args(const struct arm_boot_info *info, AddressSpace *as)int initrd_size = info->initrd_size;hwaddr base = info->loader_start;hwaddr p; +MemTxResult result; p = base +KERNEL_ARGS_ADDR ;/* ATAG_CORE */
@@ -326,8 +328,9 @@ static void set_kernel_args(const struct arm_boot_info *info, AddressSpace *as)int cmdline_size; cmdline_size =strlen (info->kernel_cmdline); -address_space_write (as, p +8 ,MEMTXATTRS_UNSPECIFIED , - info->kernel_cmdline, cmdline_size +1 ); + result =address_space_write (as, p +8 ,MEMTXATTRS_UNSPECIFIED , + info->kernel_cmdline, cmdline_size +1 ); +assert (result ==MEMTX_OK ); cmdline_size = (cmdline_size >>2 ) +1 ;WRITE_WORD (p, cmdline_size +2 );WRITE_WORD (p,0x54410009 );
@@ -341,8 +344,9 @@ static void set_kernel_args(const struct arm_boot_info *info, AddressSpace *as) atag_board_len = (info->atag_board (info, atag_board_buf) +3 ) & ~3 ;WRITE_WORD (p, (atag_board_len +8 ) >>2 );WRITE_WORD (p,0x414f4d50 ); -address_space_write (as, p,MEMTXATTRS_UNSPECIFIED , - atag_board_buf, atag_board_len); + result =address_space_write (as, p,MEMTXATTRS_UNSPECIFIED , + atag_board_buf, atag_board_len); +assert (result ==MEMTX_OK ); p += atag_board_len; }/* ATAG_END */
@@ -357,6 +361,7 @@ static void set_kernel_args_old(const struct arm_boot_info *info,const char *s;int initrd_size = info->initrd_size;hwaddr base = info->loader_start; +MemTxResult result;/* see linux/include/asm-arm/setup.h */ p = base +KERNEL_ARGS_ADDR ;
@@ -419,7 +424,9 @@ static void set_kernel_args_old(const struct arm_boot_info *info, } s = info->kernel_cmdline;if (s) { -address_space_write (as, p,MEMTXATTRS_UNSPECIFIED , s,strlen (s) +1 ); + result =address_space_write (as, p,MEMTXATTRS_UNSPECIFIED , + s,strlen (s) +1 ); +assert (result ==MEMTX_OK ); }else {WRITE_WORD (p,0 ); }
Signature · 1 line
2.21.3
Re: [PATCH v2 5/7] hw/arm/boot: Abort if set_kernel_args() fails
Quoted 7 lines · Philippe Mathieu-Daudé
If a
address_space_write()fails while callingset_kernel_args(), the guest kernel will boot
using crap data. Avoid that by aborting if this
ever occurs.Signed-off-by Philippe Mathieu-Daudé <[email protected]>
I think it's reasonable to make these be fatal, but I think we shouldn't just assert() but instead make set_kernel_arg() and set_kernel_args_old() return a success/failure indication, and report failures to the user as fatal errors.
thanks
-- PMM
RFC PATCH v2 6/7 accel/kvm: Let KVM_EXIT_MMIO return error
In reply to Philippe Mathieu-DaudéGive the hypervisor a possibility to catch any error occuring during KVM_EXIT_MMIO.
---
RFC because maybe we simply want to ignore this error instead
--- accel/kvm/kvm-all.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
accel/kvm/kvm-all.c +7 -6
@@ -2357,6 +2357,7 @@ int kvm_cpu_exec(CPUState *cpu) do { MemTxAttrs attrs; + MemTxResult res; if (cpu->vcpu_dirty) { kvm_arch_put_registers(cpu, KVM_PUT_RUNTIME_STATE);
@@ -2429,12 +2430,12 @@ int kvm_cpu_exec(CPUState *cpu)case KVM_EXIT_MMIO :DPRINTF ("handle_mmio\n" );/* Called outside BQL */ -address_space_rw (&address_space_memory, - run->mmio.phys_addr, attrs, - run->mmio.data, - run->mmio.len, - run->mmio.is_write); - ret =0 ; + res =address_space_rw (&address_space_memory, + run->mmio.phys_addr, attrs, + run->mmio.data, + run->mmio.len, + run->mmio.is_write); + ret = res ==MEMTX_OK ?0 :-1 ;break ;case KVM_EXIT_IRQ_WINDOW_OPEN :DPRINTF ("irq_window_open\n" );
Signature · 1 line
2.21.3
Re: [RFC PATCH v2 6/7] accel/kvm: Let KVM_EXIT_MMIO return error
Quoted 7 lines · Philippe Mathieu-Daudé
Give the hypervisor a possibility to catch any error occuring during
KVM_EXIT_MMIO.Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
RFC because maybe we simply want to ignore this error instead
The "right" answer is that the kernel should enhance the KVM_EXIT_MMIO API to allow userspace to say "sorry, you got a bus error on that memory access the guest just tried" (which the kernel then has to turn into an appropriate guest exception, or ignore, depending on what the architecture requires.) You don't want to set ret to non-zero here, because that will cause us to VM_STOP, and I suspect that x86 at least is relying on the implict RAZ/WI behaviour it currently gets.
thanks
-- PMM
Re: [RFC PATCH v2 6/7] accel/kvm: Let KVM_EXIT_MMIO return error
Quoted 9 lines · Peter Maydell
Quoted 7 lines · Philippe Mathieu-Daudé
Give the hypervisor a possibility to catch any error occuring during
KVM_EXIT_MMIO.Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
RFC because maybe we simply want to ignore this error instead
Quoted 8 lines
The "right" answer is that the kernel should enhance the
KVM_EXIT_MMIOAPI to allow userspace to say "sorry, you got a bus error on that memory access the guest just tried" (which the kernel then has to turn into an appropriate guest exception, or ignore, depending on what the architecture requires.) You don't want to set ret to non-zero here, because that will cause us toVM_STOP, and I suspect that x86 at least is relying on the implict RAZ/WI behaviour it currently gets.
OK, similar to the worst case I expected here.
Thank you for the clear explanation :)
Quoted 4 lines
thanks
-- PMM
Paolo Bonzini
maintainerRe: [RFC PATCH v2 6/7] accel/kvm: Let KVM_EXIT_MMIO return error
In reply to Peter MaydellQuoted 8 lines · Peter Maydell
The "right" answer is that the kernel should enhance the
KVM_EXIT_MMIOAPI to allow userspace to say "sorry, you got a bus error on that memory access the guest just tried" (which the kernel then has to turn into an appropriate guest exception, or ignore, depending on what the architecture requires.) You don't want to set ret to non-zero here, because that will cause us toVM_STOP, and I suspect that x86 at least is relying on the implict RAZ/WI behaviour it currently gets.
Yes, it is. It may even be already possible to inject the right exception (on ARM) through KVM_SET_VCPU_EVENTS or something like that, too.
Paolo
Re: [RFC PATCH v2 6/7] accel/kvm: Let KVM_EXIT_MMIO return error
Quoted 11 lines · Paolo Bonzini
Quoted 8 lines · Peter Maydell
The "right" answer is that the kernel should enhance the
KVM_EXIT_MMIOAPI to allow userspace to say "sorry, you got a bus error on that memory access the guest just tried" (which the kernel then has to turn into an appropriate guest exception, or ignore, depending on what the architecture requires.) You don't want to set ret to non-zero here, because that will cause us toVM_STOP, and I suspect that x86 at least is relying on the implict RAZ/WI behaviour it currently gets.
Quoted 2 lines
Yes, it is. It may even be already possible to inject the right exception (on ARM) through
KVM_SET_VCPU_EVENTSor something like that, too.
Yeah, in theory we could deliver an exception from userspace by updating all the register state, but I think the kernel really ought to do it both (a) because it's just a neater API to do it that way round and (b) because the kernel is the one that has the info about the faulting insn that it might need for things like setting up a syndrome register value.
thanks
-- PMM
RFC PATCH v2 7/7 hw/core/loader: Assert loading ROM regions succeeds at reset
In reply to Philippe Mathieu-DaudéIf we are unable to load a blob in a ROM region, we should not ignore it and let the machine boot.
---
RFC: Maybe more polite with user to use hw_error()?
--- hw/core/loader.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
hw/core/loader.c +6 -2
@@ -1146,8 +1146,12 @@ static void rom_reset(void *unused)void *host =memory_region_get_ram_ptr (rom->mr);memcpy (host, rom->data, rom->datasize); }else { -address_space_write_rom (rom->as, rom->addr,MEMTXATTRS_UNSPECIFIED , - rom->data, rom->datasize); +MemTxResult res; + + res =address_space_write_rom (rom->as, rom->addr, +MEMTXATTRS_UNSPECIFIED , + rom->data, rom->datasize); +assert (res ==MEMTX_OK ); }if (rom->isrom) {/* rom needs to be written only once */
Signature · 1 line
2.21.3
Re: [RFC PATCH v2 7/7] hw/core/loader: Assert loading ROM regions succeeds at reset
Quoted 17 lines · Philippe Mathieu-Daudé
If we are unable to load a blob in a ROM region, we should not ignore it and let the machine boot.
Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
RFC: Maybe more polite with user to usehw_error()?--- hw/core/loader.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)hw/core/loader.c +0
-0@@ -1146,8 +1146,12 @@ static void rom_reset(void *unused)void *host =memory_region_get_ram_ptr (rom->mr);
hw/core/loader.c static void rom_reset(void *unused) · line 1154
Quoted 10 lines
hw/core/loader.c +6
-2memcpy (host, rom->data, rom->datasize); }else { -address_space_write_rom (rom->as, rom->addr,MEMTXATTRS_UNSPECIFIED , - rom->data, rom->datasize); +MemTxResult res; + + res =address_space_write_rom (rom->as, rom->addr, +MEMTXATTRS_UNSPECIFIED , + rom->data, rom->datasize); +assert (res ==MEMTX_OK );
We shouln't assert(), because this is easy for a user to trigger by loading an ELF file that's been linked to the wrong address. Something helpful that ideally includes the name of the ELF file and perhaps the address might be nice.
(But overall I'm a bit wary of this and other patches in the series just because they add checks that were previously not there, and I'm not sure whether users might be accidentally relying on the continues-anyway behaviour.)
thanks
-- PMM
Re: [RFC PATCH v2 7/7] hw/core/loader: Assert loading ROM regions succeeds at reset
Quoted 34 lines · Peter Maydell
Quoted 17 lines · Philippe Mathieu-Daudé
If we are unable to load a blob in a ROM region, we should not ignore it and let the machine boot.
Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
RFC: Maybe more polite with user to usehw_error()?--- hw/core/loader.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)hw/core/loader.c +0
-0@@ -1146,8 +1146,12 @@ static void rom_reset(void *unused)void *host =memory_region_get_ram_ptr (rom->mr);hw/core/loader.c static void rom_reset(void *unused) · line 1154
Quoted 10 lines
hw/core/loader.c +6
-2memcpy (host, rom->data, rom->datasize); }else { -address_space_write_rom (rom->as, rom->addr,MEMTXATTRS_UNSPECIFIED , - rom->data, rom->datasize); +MemTxResult res; + + res =address_space_write_rom (rom->as, rom->addr, +MEMTXATTRS_UNSPECIFIED , + rom->data, rom->datasize); +assert (res ==MEMTX_OK );We shouln't
assert(), because this is easy for a user to trigger by loading an ELF file that's been linked to the wrong address. Something helpful that ideally includes the name of the ELF file and perhaps the address might be nice.
Quoted 4 lines
(But overall I'm a bit wary of this and other patches in the series just because they add checks that were previously not there, and I'm not sure whether users might be accidentally relying on the continues-anyway behaviour.)
I understand. Thanks for reviewing, I'll rework this one and the previous set_kernel_args().
Quoted 4 lines
thanks
-- PMM
Quoted 18 lines · Philippe Mathieu-Daudé
Various places ignore the MemTxResult indicator of transaction failed. Fix the easy places. The rest are the DMA devices, which require deeper analysis.
Since v1:
- Dropped "exec/memory: Emit warning when MemTxResult is ignored"
https://www.mail-archive.com/[email protected]/msg704180.htmlPhilippe Mathieu-Daudé (7):
exec: Let address_space_read/write_cached() propagate MemTxResult
exec: Propagatecpu_memory_rw_debug()error
disas: Letdisas::read_memory()handler return EIO on error hw/elf_ops: Do not ignore write failures when loading ELF hw/arm/boot: Abort ifset_kernel_args()fails accel/kvm: LetKVM_EXIT_MMIOreturn error hw/core/loader: Assert loading ROM regions succeeds at reset
Quoted 10 lines
include/exec/cpu-all.h | 1 + include/exec/memory.h | 19 +++++++++++-------- include/hw/elf_ops.h | 11 ++++++++--- accel/kvm/kvm-all.c | 13 +++++++------ disas.c | 13 ++++++++----- exec.c | 28 ++++++++++++++++------------ hw/arm/boot.c | 19 +++++++++++++------ hw/core/loader.c | 8 ++++++-- 8 files changed, 70 insertions(+), 42 deletions(-)
Queued patches 1-4, thanks.
Paolo