Bug 740465
Summary: | Host got crash when guest running netperf client with UDP_STREAM protocol with IPV6 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qunfang Zhang <qzhang> | ||||||
Component: | kernel | Assignee: | jason wang <jasowang> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 6.2 | CC: | acathrow, dhoward, flang, herbert.xu, herrold, jpallich, jpirko, juzhang, michen, mkenneth, pmatouse, sforsber, tburke, virt-maint, xwei | ||||||
Target Milestone: | rc | Keywords: | ZStream | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | kernel-2.6.32-211.el6 | Doc Type: | Bug Fix | ||||||
Doc Text: |
A scenario for this bug involves two hosts, configured to use IPv4 network, and two guests, configured to use IPv6 network. When a guest on host A attempted to send a large UDP datagram to host B, host A terminated unexpectedly. With this update, the ipv6_select_ident() function has been fixed to accept the in6_addr parameter and to use the destination address in IPv6 header when no route is attached, and the crashes no longer occur in the described scenario.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2011-12-06 14:14:36 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 723433, 748554, 748808 | ||||||||
Attachments: |
|
Description
Qunfang Zhang
2011-09-22 06:55:06 UTC
Created attachment 524326 [details]
Log for the host "vmcore" file
Created attachment 524327 [details]
bt information for host vmcore file
Test with the same steps with IPV4 network for 5 times, no crash happens. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. I re-test on latest rhel5.8 host, do not hit the issue. Host A (rhel5.8): kernel-2.6.18-286.el5 kvm-83-239.el5 1. Boot a rhel6.2 guest A on host A (rhel5.8), configure the ipv6 ip according to the bug description steps. (netperf client) 2. Boot another rhel6.2 guest B on another host B, configure this guest with ipv6 addr. (netserver) 3. Run netperf on guest A, the same steps as bug description too. Result: No crash happens, both host and guest work well. Qunfang, would you please test upstream stable kernel (with the patch for CVE-2011-2699 applied) if it has the same problem? Thanks. (In reply to comment #13) > Qunfang, would you please test upstream stable kernel (with the patch for > CVE-2011-2699 applied) if it has the same problem? Thanks. OK, will do it and update result here after finish. (In reply to comment #13) > Qunfang, would you please test upstream stable kernel (with the patch for > CVE-2011-2699 applied) if it has the same problem? Thanks. Hi, Jiri Sorry could you tell me where can I download a stable kernel? Thanks. (In reply to comment #15) > (In reply to comment #13) > > Qunfang, would you please test upstream stable kernel (with the patch for > > CVE-2011-2699 applied) if it has the same problem? Thanks. > > Hi, Jiri > Sorry could you tell me where can I download a stable kernel? Thanks. Usually it's on git.kernel.org (when it's up). Now I can't find it anywhere. Maybe please email greghk and ask him. Thanks. (In reply to comment #13) > Qunfang, would you please test upstream stable kernel (with the patch for > CVE-2011-2699 applied) if it has the same problem? Thanks. Hi, Jiri The issue can be reproduced with the latest stable kernel. (In reply to comment #17) > (In reply to comment #13) > > Qunfang, would you please test upstream stable kernel (with the patch for > > CVE-2011-2699 applied) if it has the same problem? Thanks. > > Hi, Jiri > The issue can be reproduced with the latest stable kernel. Okay. So there would be best to resolve this via upstream. Please report this issue via mail to netdev.org ccing author or the patch Eric Dumazet <eric.dumazet> Thanks. (In reply to comment #18) > (In reply to comment #17) > > (In reply to comment #13) > > > Qunfang, would you please test upstream stable kernel (with the patch for > > > CVE-2011-2699 applied) if it has the same problem? Thanks. > > > > Hi, Jiri > > The issue can be reproduced with the latest stable kernel. > > Okay. So there would be best to resolve this via upstream. Please report this > issue via mail to netdev.org ccing author or the patch Eric Dumazet > <eric.dumazet> > > Thanks. Ok, I have sent the mail to them. Thanks. (In reply to comment #18) > (In reply to comment #17) > > (In reply to comment #13) > > > Qunfang, would you please test upstream stable kernel (with the patch for > > > CVE-2011-2699 applied) if it has the same problem? Thanks. > > > > Hi, Jiri > > The issue can be reproduced with the latest stable kernel. > > Okay. So there would be best to resolve this via upstream. Please report this > issue via mail to netdev.org ccing author or the patch Eric Dumazet > <eric.dumazet> > > Thanks. Hello Jiri: I've reported this upstream and post a patch for -stable. Thanks Patch(es) available on kernel-2.6.32-211.el6 Verified the bug with the following packages with the same steps as bug description, and the issue does not exist any more after about 10 times attempt. kernel-2.6.32-211.el6.x86_64 qemu-kvm-0.12.1.2-2.200.el6.x86_64 So, this issue is fixed. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A scenario for this bug involves two hosts, configured to use IPv4 network, and two guests, configured to use IPv6 network. When a guest on host A attempted to send a large UDP datagram to host B, host A terminated unexpectedly. With this update, the ipv6_select_ident() function has been fixed to accept the in6_addr parameter and to use the destination address in IPv6 header when no route is attached, and the crashes no longer occur in the described scenario. 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. http://rhn.redhat.com/errata/RHSA-2011-1530.html |