Description of problem: in flight dma might be aborted partially
not reproducible found by code review and applied to RHEL6 KVM package but missing in RHEL6 because rejected by upstream.
Patch posted as Message-ID: <20100721152112.GZ24928@random.random> in rhvirt-patches.
rediffed and reposted to rhvirt-patches as Message-ID: <20100723005600.GU24928@random.random>
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Andrea, can you note why this was rejected upstream?
I submitted it to Anthony last version on 26 Feb 2009 (you can check on qemu-devel archives) and got no answer simply and apparently it wasn't applied.
(In reply to comment #7)
> I submitted it to Anthony last version on 26 Feb 2009 (you can check on
> qemu-devel archives) and got no answer simply and apparently it wasn't applied.
qemu upstream needs constant reminders; can you send out a rebased patch to the upstream list?
*** Bug 618901 has been marked as a duplicate of this bug. ***
Could you give me some suggestions how to verify this issue.?
Ok, I'm afraid there is no way to verify it. It's a "theoretical" fix for not easily reproducible issue.
The thing to verify is that this doesn't cause regressions, so you shall run some I/O intensive workload with the -drive if=ide and then run a e2fsck -f /dev/hd?? to verify the fileysystem is fine.
Verified in qemu-kvm-0.12.1.2-2.106.el6.x86_64.
1.Since bug 618901 marked as dup of this one .Verified that bug and passed.
2.Following steps comment #14.and find no bad block inode.
Based on above ,this issue has already been fixed .
Change status to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.