Bug 659594
Summary: | Kernel panic when restart network on vlan with bonding | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Liang Zheng <lzheng> | ||||
Component: | kernel | Assignee: | Neil Horman <nhorman> | ||||
Status: | CLOSED ERRATA | QA Contact: | Petr Beňas <pbenas> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 5.6 | CC: | anton, cww, dhoward, fleitner, gianluca.cecchi, jolsa, jpirko, jwest, kzhang, martin.wilck, mkarg, mmilgram, nhorman, oonkwee.lim, pbenas, pstehlik, tgraf, wmealing | ||||
Target Milestone: | rc | Keywords: | Regression, ZStream | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
A bug was discovered in the bonding driver that occurred when using netpoll and changing, adding or removing slaves from a bond. The misuse of a per-cpu flag in the bonding driver during these operations at the wrong time could lead to the detection of an invalid state in the bonding driver, triggering kernel panic. With this update, the use of the aforementioned per-cpu flag has been corrected and a kernel panic no longer occurs.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-07-21 09:54: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: | 675664, 689759, 707606 | ||||||
Attachments: |
|
Description
Liang Zheng
2010-12-03 05:40:29 UTC
It does not reproduce on 2.6.18.194-el5 so I think it is a regression bug. *** Bug 659558 has been marked as a duplicate of this bug. *** *** Bug 654600 has been marked as a duplicate of this bug. *** http://marc.info/?l=linux-netdev&m=129166237512572&w=3 I've posted a patch for this upstream, and will backport for RHEL once its accepted. http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2966935 Test build with backport 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. in kernel-2.6.18-243.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed. Hello, I have a case open for a similar problem: 00414963 You can check it for further details. My problem doesn't involve VLAN, but a rh cluster where I have 7 services, and 5 with an IP associated (so 5 ip alias defined). When I run shutdown -r with all the services running I have a panic with screeshot I'm going to attach. If I manually stop the services and then shutdown all goes well without panic. It seems that kernel-2.6.18-243.el5 solves it for me too. Created attachment 478208 [details]
panic on shutdown rh el 5.6 cluster with 5 ip alias defined on 5 services
*** Bug 679499 has been marked as a duplicate of this bug. *** *** Bug 689759 has been marked as a duplicate of this bug. *** As this problem is understood and a fix is available, when can we expect a z-stream release? Martin, very soon: https://bugzilla.redhat.com/show_bug.cgi?id=675664 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 bug was discovered in the bonding driver that occurred when using netpoll and changing, adding or removing slaves from a bond. The misuse of a per-cpu flag in the bonding driver during these operations at the wrong time could lead to the detection of an invalid state in the bonding driver, triggering kernel panic. With this update, the use of the aforementioned per-cpu flag has been corrected and a kernel panic no longer occurs. Reproduced in 2.6.18-241.el5 and verified in 2.6.18-243.el5. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-1065.html *** Bug 725849 has been marked as a duplicate of this bug. *** |