From: Thomas Huth <1878915@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.
Date: Fri, 22 May 2020 04:50:59 -0000 [thread overview]
Message-ID: <159012305970.2100.14199326277292947871.launchpad@chaenomeles.canonical.com> (raw)
In-Reply-To: 158954872808.31513.13433748579796760766.malonedeb@chaenomeles.canonical.com
** 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
next prev parent reply other threads:[~2020-05-22 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-05-22 18:59 ` felix
2020-08-20 15:36 ` 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=159012305970.2100.14199326277292947871.launchpad@chaenomeles.canonical.com \
--to=1878915@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).