Bug 839266
| Summary: | Change network with netconsole loaded cause kernel panic | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Fabian Deutsch <fdeutsch> |
| Component: | kernel | Assignee: | Jiri Benc <jbenc> |
| Status: | CLOSED ERRATA | QA Contact: | Network QE <network-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3 | CC: | acathrow, areis, bsarathy, bwang, cshao, dhoward, fdeutsch, gouyang, hadong, huiwa, jboggs, jshao, kzhang, leiwang, mburns, moli, ovirt-maint, pbenas, ycui, yuachen |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-2.6.32-294.el6 | Doc Type: | Bug Fix |
| Doc Text: |
When the netconsole module was configured over bridge and the "service network restart" command was executed, a deadlock could occur, resulting in a kernel panic. This was caused by recursive rtnl locking by both bridge and netconsole code during network interface unregistration. With this update, the rtnl lock usage is fixed, and the kernel no longer crashes in this scenario.
|
Story Points: | --- |
| Clone Of: | 825160 | Environment: | |
| Last Closed: | 2013-02-21 06:32:27 UTC | Type: | Bug |
| 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: | 825160, 842982, 846704 | ||
Hmm, never mind, 3b410a310b48a8e7de3438957635093596ad5ca5 fixes this bug. If you could still describe the setup used to reproduce this, it would be nice. (In reply to comment #3) > Hmm, never mind, 3b410a310b48a8e7de3438957635093596ad5ca5 fixes this bug. In what tree can I find this commit? > If you could still describe the setup used to reproduce this, it would be > nice. It is a plain RHEL system (VM) with kernel 2.6.32-279 and a bridge with one slave device. Do you need more details? (In reply to comment #4) > In what tree can I find this commit? Upstream vanilla, I'm backporting and testing the patch now. > It is a plain RHEL system (VM) with kernel 2.6.32-279 and a bridge with one > slave device. > Do you need more details? No, seems that I reproduced it. Thanks! This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Patch(es) available on kernel-2.6.32-294.el6 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-2013-0496.html |
Cannot reproduce; what are the exact steps to reproduce on (pure) RHEL? Any bridges involved, etc.? What kernel version was used to capture the trace in attachment 587619 [details]?