summaryrefslogtreecommitdiffstats
path: root/xlators/debug/error-gen/src/error-gen.c
diff options
context:
space:
mode:
authorRaghavendra G <raghavendra@gluster.com>2011-04-24 22:45:31 +0000
committerAnand Avati <avati@gluster.com>2011-04-29 06:59:41 -0700
commit1f06da6875d8ecff5efa2b6db387ef6084bb68a1 (patch)
tree4413eeee7b1714ee6423e1e44da883d782b513de /xlators/debug/error-gen/src/error-gen.c
parent77f485dc30e5cd81d63cb7a92dc77b3ace69d40d (diff)
performance/write-behind: initialize lock in wb-file before wb-file is set in fd-ctx.branchpoint-3.2
- Consider a combination of fuse->quick-read->read-ahead->wb->client. quick-read can do open-behind (open is returned as success even before it is issued to backend) and hence the fd can already be in the list of open fds of the inode. A flush call on some other fd opened on the same inode, will result in ra_flush issuing flush calls to all the fds opened on the same inode. This can result in wb_flush trying to hold a lock on non-initialized lock there by causing memory corruption. Signed-off-by: Raghavendra G <raghavendra@gluster.com> Signed-off-by: Anand Avati <avati@gluster.com> BUG: 2679 (Crash in GlusterFS 3.0.5 in GSP) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2679
Diffstat (limited to 'xlators/debug/error-gen/src/error-gen.c')
0 files changed, 0 insertions, 0 deletions