diff options
| author | N Balachandran <nbalacha@redhat.com> | 2019-09-25 19:50:27 +0530 |
|---|---|---|
| committer | Rinku Kothiya <rkothiya@redhat.com> | 2019-09-27 14:43:39 +0000 |
| commit | bac5d7d60d14a190217fcd84fd0803a4d6a2e37d (patch) | |
| tree | 583ba6d62319592f38f5ab0e2d620a56b3fb64a4 | |
| parent | e3942babf00fe74dd3c3fc8502482967fbdb9ca5 (diff) | |
perf/write-behind: Clear frame->local on conflict errorv7.0rc3
WB saves the wb_inode in frame->local for the truncate and
ftruncate fops. This value is not cleared in case of error
on a conflicting write request. FRAME_DESTROY finds a non-null
frame->local and tries to free it using mem_put. However,
wb_inode is allocated using GF_CALLOC, causing the
process to crash.
credit: vpolakis@gmail.com
Change-Id: I217f61470445775e05145aebe44c814731c1b8c5
fixes: bz#1755678
Signed-off-by: N Balachandran <nbalacha@redhat.com>
| -rw-r--r-- | xlators/performance/write-behind/src/write-behind.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/xlators/performance/write-behind/src/write-behind.c b/xlators/performance/write-behind/src/write-behind.c index aade1c9c563..ab6b76cace8 100644 --- a/xlators/performance/write-behind/src/write-behind.c +++ b/xlators/performance/write-behind/src/write-behind.c @@ -1522,6 +1522,10 @@ __wb_handle_failed_conflict(wb_request_t *req, wb_request_t *conflict, */ req->op_ret = -1; req->op_errno = conflict->op_errno; + if ((req->stub->fop == GF_FOP_TRUNCATE) || + (req->stub->fop == GF_FOP_FTRUNCATE)) { + req->stub->frame->local = NULL; + } list_del_init(&req->todo); list_add_tail(&req->winds, tasks); |