diff options
author | Pranith Kumar K <pkarampu@redhat.com> | 2017-09-05 13:30:53 +0530 |
---|---|---|
committer | jiffin tony Thottan <jthottan@redhat.com> | 2017-09-06 07:48:11 +0000 |
commit | f5170d49e44d0327020335de0b0fc2999a455aad (patch) | |
tree | dc2fc506d1028d4e1a098d5c417f5be8a31b38dd /tests | |
parent | 97f547c7822980aca2ec4cbbe236b930bab38b76 (diff) |
features/shard: Increment counts in locks
Backport of https://review.gluster.org/18203
Problem:
Because create_count/eexist_count are incremented without locks, all the shards may not
be created because call_count will be lesser than what it needs to be. This can lead
to crash in shard_common_inode_write_do() because inode on which we want to do
fd_anonymous() is NULL
Fix:
Increment the counts in frame->lock
>Change-Id: Ibc87dcb1021e9f4ac2929f662da07aa7662ab0d6
>BUG: 1488354
>Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Change-Id: Ibc87dcb1021e9f4ac2929f662da07aa7662ab0d6
BUG: 1488387
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Reviewed-on: https://review.gluster.org/18204
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions