Description of problem:
I suspect we need to carry this patch in RHEL 7.1:
It's not accepted upstream yet, waiting on a few more ACKs.
Version-Release number of selected component (if applicable):
Not reproducible. It's a bug that probably only breaks
Since it looks as if this patch is about to go upstream, I'm
Note that the final version is a bit different from the one
posted first. The final version is:
Miya: Can someone in your team consider this bug for QA ack?
It's difficult to QA since it doesn't cause a failure on x86
systems. Perhaps it's best to just check that the patch was
Now upstream (commit f76faeda4bd59f972d09dd9d954297f17c21dd60).
Fix included in qemu-kvm-rhev-2.1.2-8.el7
Version of components:
# rpm -ql qemu-kvm-rhev-2.1.2-8.el7.x86_64 --changelog |grep 1152901
- kvm-block-curl-Improve-type-safety-of-s-timeout.patch [bz#1152901]
- Resolves: bz#1152901
Also checked the qemu-kvm-rhev-2.1.2-8.el7.src.rpm. Decompress this rpm. Could find the same patch code(https://github.com/stefanha/qemu/commit/f76faeda4bd59f972d09dd9d954297f17c21dd60) in file ./kvm-block-curl-Improve-type-safety-of-s-timeout.patch
Based on above show, this bz has been verified.
# rpm -ql qemu-kvm-rhev-2.1.2-1.el7.x86_64 --changelog|grep 1152901
So reproduced it.
As you have mentioned in comment 2, does above verify method is correct or not? Thanks.
Yes that's fine.
We didn't actually demonstrate a bug. It probably only affects
big endian systems.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.