Bug 212122
Summary: | 2.6.9-42.19.ELsmp kernel deadlock when IPv6 address is configured on an unplugged interface | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Paul Dwyer <pdwyer> | ||||||
Component: | kernel | Assignee: | Neil Horman <nhorman> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 4.0 | CC: | davem, jbaron, nhorman, tgraf | ||||||
Target Milestone: | --- | Keywords: | Regression | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | RHBA-2007-0304 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-05-08 03: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: | |||||||||
Attachments: |
|
Description
Paul Dwyer
2006-10-25 07:58:39 UTC
If you have the system still available could you please provide a sysrq-t from when the system is hung please? It would be helpful to know which process is holding the semaphore that the above backtrace is blocked on. Thanks! Sorry, I didn't even look at the code, I assumed that another process was holding the lock, although, for the record, there is no patch posted to this bug. I'll fix it shortly though. Created attachment 139597 [details]
patch to fix addrconf deadlock
committed in stream U5 build 42.23. A test kernel with this patch is available from http://people.redhat.com/~jbaron/rhel4/ Although based on comment #7, perhaps we need to revisit this further.... No further movement is needed, really. The patch has been comitted. Nokia's observation regarding the double unlock will cause a minor gripe from the lock validator, but no real problems. I'm going to clean that up shortly, but as far as this bug is concerned, the fix is in place. I think the double unlock, if it's there, is a real bug. If we do the first unlock, another cpu grabs the lock, then we do that second bogus unlock, this allows a third cpu into the critical section erroneously which will corrupt data. It's a bug, and it can very well cause corruption, so we should fix it. Yeah, after considering it further, I agree. I'll look at it and post a repo patch if the double unlock exists. Created attachment 142170 [details]
patch to fix double unlock
I've submitted this patch to fix the double unlock condition
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. 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. ok, i've integrated the patch from comment #17. A test kernel with this patch is available from http://people.redhat.com/~jbaron/rhel4/ This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP. QE ack for RHEL4.5. Both patches are in the -51 kernel and I set an ipv6 address with the network down with no hang. 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 the 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/RHBA-2007-0304.html |