| Summary: | SETATTR stack leak? | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Krishna Srinivas <krishna> |
| Component: | fuse | Assignee: | Csaba Henk <csaba> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | amarts, anush, gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| 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: | |
PATCH: http://patches.gluster.com/patch/3164 in master (mount/fuse: Destroy STACK when truncate and other op are part of same SETATTR) PATCH: http://patches.gluster.com/patch/3165 in release-3.0 (mount/fuse: Destroy STACK when truncate and other op are part of same SETATTR) |
glusterdump had: [global.callpool] global.callpool=0x10ef1310 global.callpool.cnt=352 all the 352 calls were SETATTR looking at the code, when truncate is combined with any other operation in the same SETATTR call, it looks like there is a stack leak. fuse_setattr_cbk(): if (state->truncate_needed) { fuse_do_truncate (state, state->size); } else { when this happens the stack used for the other operation in SETATTR is not getting destroyed. This was observed in a customer environment. This does not affect the working of application making the calls though.