Bug 1786222
Summary: | glusterfs APIs used in forked process for storage labelling are not async signal safe causing deadlocks. | |||
---|---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | kylechan <kylechan> | |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | |
Status: | CLOSED DEFERRED | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | unspecified | CC: | berrange, kylechan, libvirt-maint, mprivozn | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1786301 (view as bug list) | Environment: | ||
Last Closed: | 2024-12-17 12:32:45 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: |
Description
kylechan
2019-12-24 03:38:17 UTC
Thanks for debugging this, it is a really serious problem. Unfortunately it looks like it will be pretty difficult/painful to solve too, but we definitely need to solve it :-( I agree that it is serious problem, but I don't think we have a way out here. Dan, do you have an idea? (In reply to Michal Privoznik from comment #2) > I agree that it is serious problem, but I don't think we have a way out > here. Dan, do you have an idea? I don't know enough about the glfs api, but perhaps it is enough to open the connection in the main process and let the open handle be used in the child which might then only require read/write calls. Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution. |