qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PULL 10/10] target/s390x/mmu_helper: Do not ignore address_space_rw() errors
Date: Thu, 16 Oct 2025 18:26:01 +0200	[thread overview]
Message-ID: <20251016162601.442557-11-thuth@redhat.com> (raw)
In-Reply-To: <20251016162601.442557-1-thuth@redhat.com>

From: Philippe Mathieu-Daudé <philmd@linaro.org>

If a address_space_rw() call ever fails, break the loop and
return the PGM_ADDRESSING error (after triggering an access
exception).

Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20251008141410.99865-3-philmd@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 target/s390x/mmu_helper.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/target/s390x/mmu_helper.c b/target/s390x/mmu_helper.c
index 22d3d4a97df..3b1e75f7833 100644
--- a/target/s390x/mmu_helper.c
+++ b/target/s390x/mmu_helper.c
@@ -546,9 +546,15 @@ int s390_cpu_virt_mem_rw(S390CPU *cpu, vaddr laddr, uint8_t ar, void *hostbuf,
 
         /* Copy data by stepping through the area page by page */
         for (i = 0; i < nr_pages; i++) {
+            MemTxResult res;
+
             currlen = MIN(len, TARGET_PAGE_SIZE - (laddr % TARGET_PAGE_SIZE));
-            address_space_rw(as, pages[i] | (laddr & ~TARGET_PAGE_MASK),
-                             attrs, hostbuf, currlen, is_write);
+            res = address_space_rw(as, pages[i] | (laddr & ~TARGET_PAGE_MASK),
+                                   attrs, hostbuf, currlen, is_write);
+            if (res != MEMTX_OK) {
+                ret = PGM_ADDRESSING;
+                break;
+            }
             laddr += currlen;
             hostbuf += currlen;
             len -= currlen;
-- 
2.51.0



  parent reply	other threads:[~2025-10-16 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 16:25 [PULL 00/10] Various testing and s390x patches Thomas Huth
2025-10-16 16:25 ` [PULL 01/10] python/qemu: Replace some remaining "avocados" with "functional tests" Thomas Huth
2025-10-16 16:25 ` [PULL 02/10] tests/functional/aarch64: Drop some sbsaref_alpine tests Thomas Huth
2025-10-16 16:25 ` [PULL 03/10] gitlab: purge msys pacman cache Thomas Huth
2025-10-16 16:25 ` [PULL 04/10] tests/functional: Set current time stamp of assets when using them Thomas Huth
2025-10-16 16:25 ` [PULL 05/10] tests: Evict stale files in the functional download cache after a while Thomas Huth
2025-10-16 16:25 ` [PULL 06/10] tests/functional/alpha: Remove superfluous fetch() line from the clipper test Thomas Huth
2025-10-16 16:25 ` [PULL 07/10] tests/functional: remove use of getLogger in reverse debuging Thomas Huth
2025-10-16 16:25 ` [PULL 08/10] tests/functional: ensure GDB client is stopped on error Thomas Huth
2025-10-16 16:26 ` [PULL 09/10] target/s390x/mmu_helper: Simplify s390_cpu_virt_mem_rw() logic Thomas Huth
2025-10-16 16:26 ` Thomas Huth [this message]
2025-10-17 15:12 ` [PULL 00/10] Various testing and s390x patches Richard Henderson

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=20251016162601.442557-11-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).