Bug 456649
| Summary: | xenbus suspend_mutex remains locked after transaction failure | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Ian Campbell <ijc> |
| Component: | kernel-xen | Assignee: | Andrew Jones <drjones> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.7 | CC: | clalance, ddutile, drjones, jzheng, xen-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-16 16:03:34 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: | 458302 | ||
|
Description
Ian Campbell
2008-07-25 09:52:10 UTC
Ian,
I ran the above test loop:
while : ; do xenstore-write foo bar ; done
in one dom0 window, and in another dom0, ran an infinite save/restore loop on
the domU. I could not cause the save/restore to fail/hang/stop, which is what I
would expect if xenbus transaction processing was hung due to suspend_mutex
remaining locked.
Is there some other test you can recommend ?
Without a valid regression test/cause-effect, acking the patch will be tough to
do (in 4.8).
- Don
I've just noticed the old needinfo on this bug. I could have sworn I responded at the time but I must have written it and not hit send/submit or something. My memory of this bug is very fuzzy but I think you need to run the while ... xenstore-write... loop in a domU which is being repeatedly suspended and resumed, rather than running it in the dom0 as you were doing (having a loop in both dom0 and domU can't hurt I suppose...) This is a difficult bug to recreate, but the proposed patch has been integrated into a test build at http://people.redhat.com/drjones/virttest/1-2/. The build is available for anyone who has seen the bug and would like to test the patch to see if it goes away. Also note that the link in the description pointing to the upstream patch is out of date, you can find it here now http://xenbits.xensource.com/xen-unstable.hg?rev/bbce4d115189 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. Committed in 89.42.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/ Confirmed the patch is in -94.EL. Never reproduced this. There were a few rhel4 patches that are just integrated back then this looked safe and we got runtime with them by them being integrated. I guess sanity checking is the best we can do. 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-0263.html |