| Summary: | 3.0.5 crash if compiled under fedora 12 | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
| Component: | transport | Assignee: | Raghavendra G <raghavendra> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0.5 | CC: | amarts, gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Joe Julian
2010-08-11 21:03:16 UTC
Hi, This is due to the compile flag, '-fstack-protection' in gcc. Please give '-fno-stack-protection' flag to gcc while compiling. (make clean install CFLAGS="-fno-stack-protection") This is a known issue with 3.0.x release of GlusterFS, which can't be fixed due to the limitations in its protocol structures. With 3.1.x releases it will be fixed and we should not see these crashes anymore. Closing this bug as with the above mentioned cflag this can be solved. Then shouldn't this flag be added to the spec file for the 3.0 series? |