* [PATCH v2 2/2] tests/qtest: ahci-test: add test exposing reset issue with pending callback
2023-09-06 13:09 [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Fiona Ebner
@ 2023-09-06 13:09 ` Fiona Ebner
2023-10-05 10:49 ` [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Simon Rowe
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: Fiona Ebner @ 2023-09-06 13:09 UTC (permalink / raw)
To: qemu-devel
Cc: jsnow, thuth, lvivier, pbonzini, srowe, mike.maslenkin,
qemu-block, t.lamprecht, a.lauterer, philmd, kwolf
Before commit "hw/ide: reset: cancel async DMA operation before
resetting state", this test would fail, because a reset with a
pending write operation would lead to an unsolicited write to the
first sector of the disk.
The test writes a pattern to the beginning of the disk and verifies
that it is still intact after a reset with a pending operation. It
also checks that the pending operation actually completes correctly.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
Changes in v2:
* Move variable declarations to the beginning of the function.
* Use g_autofree for malloced buffers.
* Group toghether with other reset test (hope I did it correctly).
* Use ahci_boot_and_enable() and enable throttling to make test
work independently of environment.
tests/qtest/ahci-test.c | 86 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 85 insertions(+), 1 deletion(-)
diff --git a/tests/qtest/ahci-test.c b/tests/qtest/ahci-test.c
index abab761c26..2615c9f65c 100644
--- a/tests/qtest/ahci-test.c
+++ b/tests/qtest/ahci-test.c
@@ -1424,6 +1424,89 @@ static void test_reset(void)
ahci_shutdown(ahci);
}
+static void test_reset_pending_callback(void)
+{
+ AHCIQState *ahci;
+ AHCICommand *cmd;
+ uint8_t port;
+ uint64_t ptr1;
+ uint64_t ptr2;
+
+ int bufsize = 4 * 1024;
+ int speed = bufsize + (bufsize / 2);
+ int offset1 = 0;
+ int offset2 = bufsize / AHCI_SECTOR_SIZE;
+
+ g_autofree unsigned char *tx1 = g_malloc(bufsize);
+ g_autofree unsigned char *tx2 = g_malloc(bufsize);
+ g_autofree unsigned char *rx1 = g_malloc0(bufsize);
+ g_autofree unsigned char *rx2 = g_malloc0(bufsize);
+
+ /* Uses throttling to make test independent of specific environment. */
+ ahci = ahci_boot_and_enable("-drive if=none,id=drive0,file=%s,"
+ "cache=writeback,format=%s,"
+ "throttling.bps-write=%d "
+ "-M q35 "
+ "-device ide-hd,drive=drive0 ",
+ tmp_path, imgfmt, speed);
+
+ port = ahci_port_select(ahci);
+ ahci_port_clear(ahci, port);
+
+ ptr1 = ahci_alloc(ahci, bufsize);
+ ptr2 = ahci_alloc(ahci, bufsize);
+
+ g_assert(ptr1 && ptr2);
+
+ /* Need two different patterns. */
+ do {
+ generate_pattern(tx1, bufsize, AHCI_SECTOR_SIZE);
+ generate_pattern(tx2, bufsize, AHCI_SECTOR_SIZE);
+ } while (memcmp(tx1, tx2, bufsize) == 0);
+
+ qtest_bufwrite(ahci->parent->qts, ptr1, tx1, bufsize);
+ qtest_bufwrite(ahci->parent->qts, ptr2, tx2, bufsize);
+
+ /* Write to beginning of disk to check it wasn't overwritten later. */
+ ahci_guest_io(ahci, port, CMD_WRITE_DMA_EXT, ptr1, bufsize, offset1);
+
+ /* Issue asynchronously to get a pending callback during reset. */
+ cmd = ahci_command_create(CMD_WRITE_DMA_EXT);
+ ahci_command_adjust(cmd, offset2, ptr2, bufsize, 0);
+ ahci_command_commit(ahci, cmd, port);
+ ahci_command_issue_async(ahci, cmd);
+
+ ahci_set(ahci, AHCI_GHC, AHCI_GHC_HR);
+
+ ahci_command_free(cmd);
+
+ /* Wait for throttled write to finish. */
+ sleep(1);
+
+ /* Start again. */
+ ahci_clean_mem(ahci);
+ ahci_pci_enable(ahci);
+ ahci_hba_enable(ahci);
+ port = ahci_port_select(ahci);
+ ahci_port_clear(ahci, port);
+
+ /* Read and verify. */
+ ahci_guest_io(ahci, port, CMD_READ_DMA_EXT, ptr1, bufsize, offset1);
+ qtest_bufread(ahci->parent->qts, ptr1, rx1, bufsize);
+ g_assert_cmphex(memcmp(tx1, rx1, bufsize), ==, 0);
+
+ ahci_guest_io(ahci, port, CMD_READ_DMA_EXT, ptr2, bufsize, offset2);
+ qtest_bufread(ahci->parent->qts, ptr2, rx2, bufsize);
+ g_assert_cmphex(memcmp(tx2, rx2, bufsize), ==, 0);
+
+ ahci_free(ahci, ptr1);
+ ahci_free(ahci, ptr2);
+
+ ahci_clean_mem(ahci);
+
+ ahci_shutdown(ahci);
+}
+
static void test_ncq_simple(void)
{
AHCIQState *ahci;
@@ -1945,7 +2028,8 @@ int main(int argc, char **argv)
qtest_add_func("/ahci/migrate/dma/halted", test_migrate_halted_dma);
qtest_add_func("/ahci/max", test_max);
- qtest_add_func("/ahci/reset", test_reset);
+ qtest_add_func("/ahci/reset/simple", test_reset);
+ qtest_add_func("/ahci/reset/pending_callback", test_reset_pending_callback);
qtest_add_func("/ahci/io/ncq/simple", test_ncq_simple);
qtest_add_func("/ahci/migrate/ncq/simple", test_migrate_ncq);
--
2.39.2
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state
2023-09-06 13:09 [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Fiona Ebner
2023-09-06 13:09 ` [PATCH v2 2/2] tests/qtest: ahci-test: add test exposing reset issue with pending callback Fiona Ebner
@ 2023-10-05 10:49 ` Simon Rowe
2023-10-24 10:54 ` Fiona Ebner
2023-10-26 6:17 ` Michael Tokarev
3 siblings, 0 replies; 7+ messages in thread
From: Simon Rowe @ 2023-10-05 10:49 UTC (permalink / raw)
To: Fiona Ebner, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, thuth@redhat.com, lvivier@redhat.com,
pbonzini@redhat.com, srowe@mose.org.uk, mike.maslenkin@gmail.com,
qemu-block@nongnu.org, t.lamprecht@proxmox.com,
a.lauterer@proxmox.com, philmd@linaro.org, kwolf@redhat.com
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On Wednesday, 6 September 2023 Fiona Ebner <f.ebner@proxmox.com> wrote:
> If there is a pending DMA operation during ide_bus_reset(), the fact
> that the IDEState is already reset before the operation is canceled
> can be problematic. In particular, ide_dma_cb() might be called and
> then use the reset IDEState which contains the signature after the
> reset. When used to construct the IO operation this leads to
> ide_get_sector() returning 0 and nsector being 1. This is particularly
> bad, because a write command will thus destroy the first sector which
> often contains a partition table or similar.
Tested-by: simon.rowe@nutanix.com
[-- Attachment #2: Type: text/html, Size: 2611 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state
2023-09-06 13:09 [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Fiona Ebner
2023-09-06 13:09 ` [PATCH v2 2/2] tests/qtest: ahci-test: add test exposing reset issue with pending callback Fiona Ebner
2023-10-05 10:49 ` [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Simon Rowe
@ 2023-10-24 10:54 ` Fiona Ebner
2023-10-24 11:57 ` Philippe Mathieu-Daudé
2023-10-26 6:17 ` Michael Tokarev
3 siblings, 1 reply; 7+ messages in thread
From: Fiona Ebner @ 2023-10-24 10:54 UTC (permalink / raw)
To: qemu-devel
Cc: jsnow, thuth, lvivier, pbonzini, srowe, mike.maslenkin,
qemu-block, t.lamprecht, a.lauterer, philmd, kwolf
Ping
Am 06.09.23 um 15:09 schrieb Fiona Ebner:
> If there is a pending DMA operation during ide_bus_reset(), the fact
> that the IDEState is already reset before the operation is canceled
> can be problematic. In particular, ide_dma_cb() might be called and
> then use the reset IDEState which contains the signature after the
> reset. When used to construct the IO operation this leads to
> ide_get_sector() returning 0 and nsector being 1. This is particularly
> bad, because a write command will thus destroy the first sector which
> often contains a partition table or similar.
>
> Traces showing the unsolicited write happening with IDEState
> 0x5595af6949d0 being used after reset:
>
>> ahci_port_write ahci(0x5595af6923f0)[0]: port write [reg:PxSCTL] @ 0x2c: 0x00000300
>> ahci_reset_port ahci(0x5595af6923f0)[0]: reset port
>> ide_reset IDEstate 0x5595af6949d0
>> ide_reset IDEstate 0x5595af694da8
>> ide_bus_reset_aio aio_cancel
>> dma_aio_cancel dbs=0x7f64600089a0
>> dma_blk_cb dbs=0x7f64600089a0 ret=0
>> dma_complete dbs=0x7f64600089a0 ret=0 cb=0x5595acd40b30
>> ahci_populate_sglist ahci(0x5595af6923f0)[0]
>> ahci_dma_prepare_buf ahci(0x5595af6923f0)[0]: prepare buf limit=512 prepared=512
>> ide_dma_cb IDEState 0x5595af6949d0; sector_num=0 n=1 cmd=DMA WRITE
>> dma_blk_io dbs=0x7f6420802010 bs=0x5595ae2c6c30 offset=0 to_dev=1
>> dma_blk_cb dbs=0x7f6420802010 ret=0
>
>> (gdb) p *qiov
>> $11 = {iov = 0x7f647c76d840, niov = 1, {{nalloc = 1, local_iov = {iov_base = 0x0,
>> iov_len = 512}}, {__pad = "\001\000\000\000\000\000\000\000\000\000\000",
>> size = 512}}}
>> (gdb) bt
>> #0 blk_aio_pwritev (blk=0x5595ae2c6c30, offset=0, qiov=0x7f6420802070, flags=0,
>> cb=0x5595ace6f0b0 <dma_blk_cb>, opaque=0x7f6420802010)
>> at ../block/block-backend.c:1682
>> #1 0x00005595ace6f185 in dma_blk_cb (opaque=0x7f6420802010, ret=<optimized out>)
>> at ../softmmu/dma-helpers.c:179
>> #2 0x00005595ace6f778 in dma_blk_io (ctx=0x5595ae0609f0,
>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>> io_func=io_func@entry=0x5595ace6ee30 <dma_blk_write_io_func>,
>> io_func_opaque=io_func_opaque@entry=0x5595ae2c6c30,
>> cb=0x5595acd40b30 <ide_dma_cb>, opaque=0x5595af6949d0,
>> dir=DMA_DIRECTION_TO_DEVICE) at ../softmmu/dma-helpers.c:244
>> #3 0x00005595ace6f90a in dma_blk_write (blk=0x5595ae2c6c30,
>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>> cb=cb@entry=0x5595acd40b30 <ide_dma_cb>, opaque=opaque@entry=0x5595af6949d0)
>> at ../softmmu/dma-helpers.c:280
>> #4 0x00005595acd40e18 in ide_dma_cb (opaque=0x5595af6949d0, ret=<optimized out>)
>> at ../hw/ide/core.c:953
>> #5 0x00005595ace6f319 in dma_complete (ret=0, dbs=0x7f64600089a0)
>> at ../softmmu/dma-helpers.c:107
>> #6 dma_blk_cb (opaque=0x7f64600089a0, ret=0) at ../softmmu/dma-helpers.c:127
>> #7 0x00005595ad12227d in blk_aio_complete (acb=0x7f6460005b10)
>> at ../block/block-backend.c:1527
>> #8 blk_aio_complete (acb=0x7f6460005b10) at ../block/block-backend.c:1524
>> #9 blk_aio_write_entry (opaque=0x7f6460005b10) at ../block/block-backend.c:1594
>> #10 0x00005595ad258cfb in coroutine_trampoline (i0=<optimized out>,
>> i1=<optimized out>) at ../util/coroutine-ucontext.c:177
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state
2023-10-24 10:54 ` Fiona Ebner
@ 2023-10-24 11:57 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; 7+ messages in thread
From: Philippe Mathieu-Daudé @ 2023-10-24 11:57 UTC (permalink / raw)
To: Fiona Ebner, qemu-devel
Cc: jsnow, thuth, lvivier, pbonzini, srowe, mike.maslenkin,
qemu-block, t.lamprecht, a.lauterer, kwolf
On 24/10/23 12:54, Fiona Ebner wrote:
> Ping
John seems busy, I'll take these 2 patches. Thanks Fiona!
> Am 06.09.23 um 15:09 schrieb Fiona Ebner:
>> If there is a pending DMA operation during ide_bus_reset(), the fact
>> that the IDEState is already reset before the operation is canceled
>> can be problematic. In particular, ide_dma_cb() might be called and
>> then use the reset IDEState which contains the signature after the
>> reset. When used to construct the IO operation this leads to
>> ide_get_sector() returning 0 and nsector being 1. This is particularly
>> bad, because a write command will thus destroy the first sector which
>> often contains a partition table or similar.
>>
>> Traces showing the unsolicited write happening with IDEState
>> 0x5595af6949d0 being used after reset:
>>
>>> ahci_port_write ahci(0x5595af6923f0)[0]: port write [reg:PxSCTL] @ 0x2c: 0x00000300
>>> ahci_reset_port ahci(0x5595af6923f0)[0]: reset port
>>> ide_reset IDEstate 0x5595af6949d0
>>> ide_reset IDEstate 0x5595af694da8
>>> ide_bus_reset_aio aio_cancel
>>> dma_aio_cancel dbs=0x7f64600089a0
>>> dma_blk_cb dbs=0x7f64600089a0 ret=0
>>> dma_complete dbs=0x7f64600089a0 ret=0 cb=0x5595acd40b30
>>> ahci_populate_sglist ahci(0x5595af6923f0)[0]
>>> ahci_dma_prepare_buf ahci(0x5595af6923f0)[0]: prepare buf limit=512 prepared=512
>>> ide_dma_cb IDEState 0x5595af6949d0; sector_num=0 n=1 cmd=DMA WRITE
>>> dma_blk_io dbs=0x7f6420802010 bs=0x5595ae2c6c30 offset=0 to_dev=1
>>> dma_blk_cb dbs=0x7f6420802010 ret=0
>>
>>> (gdb) p *qiov
>>> $11 = {iov = 0x7f647c76d840, niov = 1, {{nalloc = 1, local_iov = {iov_base = 0x0,
>>> iov_len = 512}}, {__pad = "\001\000\000\000\000\000\000\000\000\000\000",
>>> size = 512}}}
>>> (gdb) bt
>>> #0 blk_aio_pwritev (blk=0x5595ae2c6c30, offset=0, qiov=0x7f6420802070, flags=0,
>>> cb=0x5595ace6f0b0 <dma_blk_cb>, opaque=0x7f6420802010)
>>> at ../block/block-backend.c:1682
>>> #1 0x00005595ace6f185 in dma_blk_cb (opaque=0x7f6420802010, ret=<optimized out>)
>>> at ../softmmu/dma-helpers.c:179
>>> #2 0x00005595ace6f778 in dma_blk_io (ctx=0x5595ae0609f0,
>>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>>> io_func=io_func@entry=0x5595ace6ee30 <dma_blk_write_io_func>,
>>> io_func_opaque=io_func_opaque@entry=0x5595ae2c6c30,
>>> cb=0x5595acd40b30 <ide_dma_cb>, opaque=0x5595af6949d0,
>>> dir=DMA_DIRECTION_TO_DEVICE) at ../softmmu/dma-helpers.c:244
>>> #3 0x00005595ace6f90a in dma_blk_write (blk=0x5595ae2c6c30,
>>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>>> cb=cb@entry=0x5595acd40b30 <ide_dma_cb>, opaque=opaque@entry=0x5595af6949d0)
>>> at ../softmmu/dma-helpers.c:280
>>> #4 0x00005595acd40e18 in ide_dma_cb (opaque=0x5595af6949d0, ret=<optimized out>)
>>> at ../hw/ide/core.c:953
>>> #5 0x00005595ace6f319 in dma_complete (ret=0, dbs=0x7f64600089a0)
>>> at ../softmmu/dma-helpers.c:107
>>> #6 dma_blk_cb (opaque=0x7f64600089a0, ret=0) at ../softmmu/dma-helpers.c:127
>>> #7 0x00005595ad12227d in blk_aio_complete (acb=0x7f6460005b10)
>>> at ../block/block-backend.c:1527
>>> #8 blk_aio_complete (acb=0x7f6460005b10) at ../block/block-backend.c:1524
>>> #9 blk_aio_write_entry (opaque=0x7f6460005b10) at ../block/block-backend.c:1594
>>> #10 0x00005595ad258cfb in coroutine_trampoline (i0=<optimized out>,
>>> i1=<optimized out>) at ../util/coroutine-ucontext.c:177
>>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state
2023-09-06 13:09 [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state Fiona Ebner
` (2 preceding siblings ...)
2023-10-24 10:54 ` Fiona Ebner
@ 2023-10-26 6:17 ` Michael Tokarev
2023-10-27 7:21 ` Fiona Ebner
3 siblings, 1 reply; 7+ messages in thread
From: Michael Tokarev @ 2023-10-26 6:17 UTC (permalink / raw)
To: Fiona Ebner, qemu-devel
Cc: jsnow, thuth, lvivier, pbonzini, srowe, mike.maslenkin,
qemu-block, t.lamprecht, a.lauterer, philmd, kwolf
06.09.2023 16:09, Fiona Ebner wrote:
> If there is a pending DMA operation during ide_bus_reset(), the fact
> that the IDEState is already reset before the operation is canceled
> can be problematic. In particular, ide_dma_cb() might be called and
> then use the reset IDEState which contains the signature after the
> reset. When used to construct the IO operation this leads to
> ide_get_sector() returning 0 and nsector being 1. This is particularly
> bad, because a write command will thus destroy the first sector which
> often contains a partition table or similar.
>
> Traces showing the unsolicited write happening with IDEState
> 0x5595af6949d0 being used after reset:
>
>> ahci_port_write ahci(0x5595af6923f0)[0]: port write [reg:PxSCTL] @ 0x2c: 0x00000300
>> ahci_reset_port ahci(0x5595af6923f0)[0]: reset port
>> ide_reset IDEstate 0x5595af6949d0
>> ide_reset IDEstate 0x5595af694da8
>> ide_bus_reset_aio aio_cancel
>> dma_aio_cancel dbs=0x7f64600089a0
>> dma_blk_cb dbs=0x7f64600089a0 ret=0
>> dma_complete dbs=0x7f64600089a0 ret=0 cb=0x5595acd40b30
>> ahci_populate_sglist ahci(0x5595af6923f0)[0]
>> ahci_dma_prepare_buf ahci(0x5595af6923f0)[0]: prepare buf limit=512 prepared=512
>> ide_dma_cb IDEState 0x5595af6949d0; sector_num=0 n=1 cmd=DMA WRITE
>> dma_blk_io dbs=0x7f6420802010 bs=0x5595ae2c6c30 offset=0 to_dev=1
>> dma_blk_cb dbs=0x7f6420802010 ret=0
>
>> (gdb) p *qiov
>> $11 = {iov = 0x7f647c76d840, niov = 1, {{nalloc = 1, local_iov = {iov_base = 0x0,
>> iov_len = 512}}, {__pad = "\001\000\000\000\000\000\000\000\000\000\000",
>> size = 512}}}
>> (gdb) bt
>> #0 blk_aio_pwritev (blk=0x5595ae2c6c30, offset=0, qiov=0x7f6420802070, flags=0,
>> cb=0x5595ace6f0b0 <dma_blk_cb>, opaque=0x7f6420802010)
>> at ../block/block-backend.c:1682
>> #1 0x00005595ace6f185 in dma_blk_cb (opaque=0x7f6420802010, ret=<optimized out>)
>> at ../softmmu/dma-helpers.c:179
>> #2 0x00005595ace6f778 in dma_blk_io (ctx=0x5595ae0609f0,
>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>> io_func=io_func@entry=0x5595ace6ee30 <dma_blk_write_io_func>,
>> io_func_opaque=io_func_opaque@entry=0x5595ae2c6c30,
>> cb=0x5595acd40b30 <ide_dma_cb>, opaque=0x5595af6949d0,
>> dir=DMA_DIRECTION_TO_DEVICE) at ../softmmu/dma-helpers.c:244
>> #3 0x00005595ace6f90a in dma_blk_write (blk=0x5595ae2c6c30,
>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0, align=align@entry=512,
>> cb=cb@entry=0x5595acd40b30 <ide_dma_cb>, opaque=opaque@entry=0x5595af6949d0)
>> at ../softmmu/dma-helpers.c:280
>> #4 0x00005595acd40e18 in ide_dma_cb (opaque=0x5595af6949d0, ret=<optimized out>)
>> at ../hw/ide/core.c:953
>> #5 0x00005595ace6f319 in dma_complete (ret=0, dbs=0x7f64600089a0)
>> at ../softmmu/dma-helpers.c:107
>> #6 dma_blk_cb (opaque=0x7f64600089a0, ret=0) at ../softmmu/dma-helpers.c:127
>> #7 0x00005595ad12227d in blk_aio_complete (acb=0x7f6460005b10)
>> at ../block/block-backend.c:1527
>> #8 blk_aio_complete (acb=0x7f6460005b10) at ../block/block-backend.c:1524
>> #9 blk_aio_write_entry (opaque=0x7f6460005b10) at ../block/block-backend.c:1594
>> #10 0x00005595ad258cfb in coroutine_trampoline (i0=<optimized out>,
>> i1=<optimized out>) at ../util/coroutine-ucontext.c:177
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Ping? Has this bugfix been lost somehow?
/mjt
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2 1/2] hw/ide: reset: cancel async DMA operation before resetting state
2023-10-26 6:17 ` Michael Tokarev
@ 2023-10-27 7:21 ` Fiona Ebner
0 siblings, 0 replies; 7+ messages in thread
From: Fiona Ebner @ 2023-10-27 7:21 UTC (permalink / raw)
To: Michael Tokarev, qemu-devel
Cc: jsnow, thuth, lvivier, pbonzini, srowe, mike.maslenkin,
qemu-block, t.lamprecht, a.lauterer, philmd, kwolf, qemu-stable
Am 26.10.23 um 08:17 schrieb Michael Tokarev:
> 06.09.2023 16:09, Fiona Ebner wrote:
>> If there is a pending DMA operation during ide_bus_reset(), the fact
>> that the IDEState is already reset before the operation is canceled
>> can be problematic. In particular, ide_dma_cb() might be called and
>> then use the reset IDEState which contains the signature after the
>> reset. When used to construct the IO operation this leads to
>> ide_get_sector() returning 0 and nsector being 1. This is particularly
>> bad, because a write command will thus destroy the first sector which
>> often contains a partition table or similar.
>>
>> Traces showing the unsolicited write happening with IDEState
>> 0x5595af6949d0 being used after reset:
>>
>>> ahci_port_write ahci(0x5595af6923f0)[0]: port write [reg:PxSCTL] @
>>> 0x2c: 0x00000300
>>> ahci_reset_port ahci(0x5595af6923f0)[0]: reset port
>>> ide_reset IDEstate 0x5595af6949d0
>>> ide_reset IDEstate 0x5595af694da8
>>> ide_bus_reset_aio aio_cancel
>>> dma_aio_cancel dbs=0x7f64600089a0
>>> dma_blk_cb dbs=0x7f64600089a0 ret=0
>>> dma_complete dbs=0x7f64600089a0 ret=0 cb=0x5595acd40b30
>>> ahci_populate_sglist ahci(0x5595af6923f0)[0]
>>> ahci_dma_prepare_buf ahci(0x5595af6923f0)[0]: prepare buf limit=512
>>> prepared=512
>>> ide_dma_cb IDEState 0x5595af6949d0; sector_num=0 n=1 cmd=DMA WRITE
>>> dma_blk_io dbs=0x7f6420802010 bs=0x5595ae2c6c30 offset=0 to_dev=1
>>> dma_blk_cb dbs=0x7f6420802010 ret=0
>>
>>> (gdb) p *qiov
>>> $11 = {iov = 0x7f647c76d840, niov = 1, {{nalloc = 1, local_iov =
>>> {iov_base = 0x0,
>>> iov_len = 512}}, {__pad =
>>> "\001\000\000\000\000\000\000\000\000\000\000",
>>> size = 512}}}
>>> (gdb) bt
>>> #0 blk_aio_pwritev (blk=0x5595ae2c6c30, offset=0,
>>> qiov=0x7f6420802070, flags=0,
>>> cb=0x5595ace6f0b0 <dma_blk_cb>, opaque=0x7f6420802010)
>>> at ../block/block-backend.c:1682
>>> #1 0x00005595ace6f185 in dma_blk_cb (opaque=0x7f6420802010,
>>> ret=<optimized out>)
>>> at ../softmmu/dma-helpers.c:179
>>> #2 0x00005595ace6f778 in dma_blk_io (ctx=0x5595ae0609f0,
>>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0,
>>> align=align@entry=512,
>>> io_func=io_func@entry=0x5595ace6ee30 <dma_blk_write_io_func>,
>>> io_func_opaque=io_func_opaque@entry=0x5595ae2c6c30,
>>> cb=0x5595acd40b30 <ide_dma_cb>, opaque=0x5595af6949d0,
>>> dir=DMA_DIRECTION_TO_DEVICE) at ../softmmu/dma-helpers.c:244
>>> #3 0x00005595ace6f90a in dma_blk_write (blk=0x5595ae2c6c30,
>>> sg=sg@entry=0x5595af694d00, offset=offset@entry=0,
>>> align=align@entry=512,
>>> cb=cb@entry=0x5595acd40b30 <ide_dma_cb>,
>>> opaque=opaque@entry=0x5595af6949d0)
>>> at ../softmmu/dma-helpers.c:280
>>> #4 0x00005595acd40e18 in ide_dma_cb (opaque=0x5595af6949d0,
>>> ret=<optimized out>)
>>> at ../hw/ide/core.c:953
>>> #5 0x00005595ace6f319 in dma_complete (ret=0, dbs=0x7f64600089a0)
>>> at ../softmmu/dma-helpers.c:107
>>> #6 dma_blk_cb (opaque=0x7f64600089a0, ret=0) at
>>> ../softmmu/dma-helpers.c:127
>>> #7 0x00005595ad12227d in blk_aio_complete (acb=0x7f6460005b10)
>>> at ../block/block-backend.c:1527
>>> #8 blk_aio_complete (acb=0x7f6460005b10) at
>>> ../block/block-backend.c:1524
>>> #9 blk_aio_write_entry (opaque=0x7f6460005b10) at
>>> ../block/block-backend.c:1594
>>> #10 0x00005595ad258cfb in coroutine_trampoline (i0=<optimized out>,
>>> i1=<optimized out>) at ../util/coroutine-ucontext.c:177
>>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
> Ping? Has this bugfix been lost somehow?
>
I sent a ping 2 days ago and it'll be picked up by Philippe :)
https://lists.nongnu.org/archive/html/qemu-devel/2023-10/msg08296.html
And CC-ing stable. Sorry, didn't think about that before.
Best Regards,
Fiona
^ permalink raw reply [flat|nested] 7+ messages in thread