From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Bin Meng" <bin.meng@windriver.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-block@nongnu.org, "David Hildenbrand" <david@redhat.com>,
"Jason Wang" <jasowang@redhat.com>, "Li Qiang" <liq3ea@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Xu" <peterx@redhat.com>,
"Qiuhao Li" <Qiuhao.Li@outlook.com>,
"Darren Kenny" <darren.kenny@oracle.com>,
"Bandan Das" <bsd@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Edgar E . Iglesias" <edgar.iglesias@gmail.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH 1/3] hw/sd/sdhci: Honor failed DMA transactions
Date: Fri, 18 Mar 2022 19:35:40 +0100 [thread overview]
Message-ID: <44a2aec2-93ea-ab57-e1b1-2a47bd91e262@redhat.com> (raw)
In-Reply-To: <20211215205656.488940-2-philmd@redhat.com>
On 15/12/2021 21.56, Philippe Mathieu-Daudé wrote:
> From: Philippe Mathieu-Daudé <f4bug@amsat.org>
>
> DMA transactions might fail. The DMA API returns a MemTxResult,
> indicating such failures. Do not ignore it. On failure, raise
> the ADMA error flag and eventually triggering an IRQ (see spec
> chapter 1.13.5: "ADMA2 States").
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> hw/sd/sdhci.c | 34 +++++++++++++++++++++++++---------
> 1 file changed, 25 insertions(+), 9 deletions(-)
>
> diff --git a/hw/sd/sdhci.c b/hw/sd/sdhci.c
> index e0bbc903446..fe2f21f0c37 100644
> --- a/hw/sd/sdhci.c
> +++ b/hw/sd/sdhci.c
> @@ -742,6 +742,7 @@ static void sdhci_do_adma(SDHCIState *s)
> unsigned int begin, length;
> const uint16_t block_size = s->blksize & BLOCK_SIZE_MASK;
> ADMADescr dscr = {};
> + MemTxResult res;
> int i;
>
> if (s->trnmod & SDHC_TRNS_BLK_CNT_EN && !s->blkcnt) {
> @@ -790,10 +791,13 @@ static void sdhci_do_adma(SDHCIState *s)
> s->data_count = block_size;
> length -= block_size - begin;
> }
> - dma_memory_write(s->dma_as, dscr.addr,
> - &s->fifo_buffer[begin],
> - s->data_count - begin,
> - MEMTXATTRS_UNSPECIFIED);
> + res = dma_memory_write(s->dma_as, dscr.addr,
> + &s->fifo_buffer[begin],
> + s->data_count - begin,
> + MEMTXATTRS_UNSPECIFIED);
> + if (res != MEMTX_OK) {
> + break;
> + }
> dscr.addr += s->data_count - begin;
> if (s->data_count == block_size) {
> s->data_count = 0;
> @@ -816,10 +820,13 @@ static void sdhci_do_adma(SDHCIState *s)
> s->data_count = block_size;
> length -= block_size - begin;
> }
> - dma_memory_read(s->dma_as, dscr.addr,
> - &s->fifo_buffer[begin],
> - s->data_count - begin,
> - MEMTXATTRS_UNSPECIFIED);
> + res = dma_memory_read(s->dma_as, dscr.addr,
> + &s->fifo_buffer[begin],
> + s->data_count - begin,
> + MEMTXATTRS_UNSPECIFIED);
> + if (res != MEMTX_OK) {
> + break;
> + }
> dscr.addr += s->data_count - begin;
> if (s->data_count == block_size) {
> sdbus_write_data(&s->sdbus, s->fifo_buffer, block_size);
> @@ -833,7 +840,16 @@ static void sdhci_do_adma(SDHCIState *s)
> }
> }
> }
> - s->admasysaddr += dscr.incr;
> + if (res != MEMTX_OK) {
> + if (s->errintstsen & SDHC_EISEN_ADMAERR) {
> + trace_sdhci_error("Set ADMA error flag");
> + s->errintsts |= SDHC_EIS_ADMAERR;
> + s->norintsts |= SDHC_NIS_ERR;
> + }
> + sdhci_update_irq(s);
> + } else {
> + s->admasysaddr += dscr.incr;
> + }
> break;
> case SDHC_ADMA_ATTR_ACT_LINK: /* link to next descriptor table */
> s->admasysaddr = dscr.addr;
Patch looks sane to me:
Reviewed-by: Thomas Huth <thuth@redhat.com>
Are you still considering it or did you drop this from your TODO list?
(since it was just marked as RFC?)
Thomas
next prev parent reply other threads:[~2022-03-18 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:56 [RFC PATCH 0/3] hw/sd/sdhci: Fix DMA re-entrancy issue Philippe Mathieu-Daudé
2021-12-15 20:56 ` [RFC PATCH 1/3] hw/sd/sdhci: Honor failed DMA transactions Philippe Mathieu-Daudé
2022-03-18 18:35 ` Thomas Huth [this message]
2021-12-15 20:56 ` [RFC PATCH 2/3] hw/sd/sdhci: Prohibit DMA accesses to devices Philippe Mathieu-Daudé
2021-12-16 3:14 ` Jason Wang
2022-03-18 18:38 ` Thomas Huth
2021-12-15 20:56 ` [RFC PATCH 3/3] tests/qtest/fuzz-sdcard-test: Add reproducer for OSS-Fuzz (Issue 29225) Philippe Mathieu-Daudé
2022-01-18 12:41 ` Thomas Huth
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=44a2aec2-93ea-ab57-e1b1-2a47bd91e262@redhat.com \
--to=thuth@redhat.com \
--cc=Qiuhao.Li@outlook.com \
--cc=alxndr@bu.edu \
--cc=bin.meng@windriver.com \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=david@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=liq3ea@gmail.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).