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.