[Bugs] [Bug 1488391] gluster-blockd process crashed and core generated
bugzilla at redhat.com
bugzilla at redhat.com
Sun Sep 17 12:48:10 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1488391
--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18206 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit 6c6abbf2662ac48cd3626c50f7fea87bfd0f76bf
Author: Pranith Kumar K <pkarampu at redhat.com>
Date: Tue Sep 5 13:30:53 2017 +0530
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 at redhat.com>
Change-Id: Ibc87dcb1021e9f4ac2929f662da07aa7662ab0d6
BUG: 1488391
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: https://review.gluster.org/18206
Smoke: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Krutika Dhananjay <kdhananj at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list