* [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
@ 2020-05-15 13:18 felix
2020-05-17 10:39 ` [Bug 1878915] " felix
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: felix @ 2020-05-15 13:18 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: floppy io-uring
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
New
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
@ 2020-05-17 10:39 ` felix
2020-05-21 14:04 ` Stefan Hajnoczi
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: felix @ 2020-05-17 10:39 UTC (permalink / raw)
To: qemu-devel
** Description changed:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
- Stack trace of thread 31002:
- #0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
- #1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
- #2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
- #3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
- #4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
- #5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
- #6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
- #7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
- #8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
- #9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
- #10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
- #11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
- #12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
- #13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
- #14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
- #15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
- #16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
- #17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
- #18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
- #19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
- #20 0x00000000b06d9fdc n/a (n/a + 0x0)
+ Stack trace of thread 31002:
+ #0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
+ #1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
+ #2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
+ #3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
+ #4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
+ #5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
+ #6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
+ #7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
+ #8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
+ #9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
+ #10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
+ #11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
+ #12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
+ #13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
+ #14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
+ #15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
+ #16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
+ #17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
+ #18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
+ #19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
+ #20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
New
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
2020-05-17 10:39 ` [Bug 1878915] " felix
@ 2020-05-21 14:04 ` Stefan Hajnoczi
2020-05-22 4:50 ` Thomas Huth
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Stefan Hajnoczi @ 2020-05-21 14:04 UTC (permalink / raw)
To: qemu-devel
Hi,
This issue should no longer occur in qemu.git/master.
Commit ba607ca8bff4d2c2062902f8355657c865ac7c29 ("aio-posix: disable
fdmon-io_uring when GSource is used") disabled fdmon-io_uring in this
scenario.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
New
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
2020-05-17 10:39 ` [Bug 1878915] " felix
2020-05-21 14:04 ` Stefan Hajnoczi
@ 2020-05-22 4:50 ` Thomas Huth
2020-05-22 18:59 ` felix
2020-08-20 15:36 ` Thomas Huth
4 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2020-05-22 4:50 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
Fix Committed
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
` (2 preceding siblings ...)
2020-05-22 4:50 ` Thomas Huth
@ 2020-05-22 18:59 ` felix
2020-08-20 15:36 ` Thomas Huth
4 siblings, 0 replies; 6+ messages in thread
From: felix @ 2020-05-22 18:59 UTC (permalink / raw)
To: qemu-devel
Confirming that I can no longer reproduce the bug with the latest master
(ae3aa5da96f4ccf0c2a28851449d92db9fcfad71). I have not bisected the bug,
though; at the moment I am not quite able to afford the time.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
Fix Committed
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
` (3 preceding siblings ...)
2020-05-22 18:59 ` felix
@ 2020-08-20 15:36 ` Thomas Huth
4 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2020-08-20 15:36 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878915
Title:
util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Status in QEMU:
Fix Released
Bug description:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0x00000000b7faf1cd __kernel_vsyscall (linux-gate.so.1 + 0x11cd)
#1 0x00000000b6c618e2 __libc_signal_restore_set (libc.so.6 + 0x348e2)
#2 0x00000000b6c4a309 __GI_abort (libc.so.6 + 0x1d309)
#3 0x00000000b6c4a1d1 __assert_fail_base (libc.so.6 + 0x1d1d1)
#4 0x00000000b6c59929 __GI___assert_fail (libc.so.6 + 0x2c929)
#5 0x0000000000ba80be get_sqe (qemu-system-i386 + 0x6d00be)
#6 0x0000000000ba80cb add_poll_add_sqe (qemu-system-i386 + 0x6d00cb)
#7 0x0000000000ba820c fill_sq_ring (qemu-system-i386 + 0x6d020c)
#8 0x0000000000ba7145 aio_poll (qemu-system-i386 + 0x6cf145)
#9 0x0000000000aede63 blk_prw (qemu-system-i386 + 0x615e63)
#10 0x0000000000aeef95 blk_pread (qemu-system-i386 + 0x616f95)
#11 0x00000000008abbfa fdctrl_transfer_handler (qemu-system-i386 + 0x3d3bfa)
#12 0x0000000000906c3d i8257_channel_run (qemu-system-i386 + 0x42ec3d)
#13 0x00000000008ac119 fdctrl_start_transfer (qemu-system-i386 + 0x3d4119)
#14 0x00000000008ab233 fdctrl_write_data (qemu-system-i386 + 0x3d3233)
#15 0x0000000000708ae7 memory_region_write_accessor (qemu-system-i386 + 0x230ae7)
#16 0x00000000007059e1 access_with_adjusted_size (qemu-system-i386 + 0x22d9e1)
#17 0x000000000070b931 memory_region_dispatch_write (qemu-system-i386 + 0x233931)
#18 0x00000000006a87a2 address_space_stb (qemu-system-i386 + 0x1d07a2)
#19 0x0000000000829216 helper_outb (qemu-system-i386 + 0x351216)
#20 0x00000000b06d9fdc n/a (n/a + 0x0)
Steps:
0. qemu-img create -f raw fda.img 3840K
1. mformat -i fda.img -n 48 -t 80 -h 2
2. qemu-system-i386 -fda fda.img -hda freedos.qcow2
3. Attempt to run 'dosfsck a:' in the guest
According to hw/block/fdc.c, a 3840K image should result in a virtual
floppy with a geometry of 48 sectors/track x 80 tracks x 2 sides.
The assert seems bogus either way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878915/+subscriptions
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-08-20 15:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-15 13:18 [Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed felix
2020-05-17 10:39 ` [Bug 1878915] " felix
2020-05-21 14:04 ` Stefan Hajnoczi
2020-05-22 4:50 ` Thomas Huth
2020-05-22 18:59 ` felix
2020-08-20 15:36 ` Thomas Huth
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).