summaryrefslogtreecommitdiffstats
path: root/extras/run-gluster.tmpfiles.in
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2016-11-18 13:30:08 +0530
committerRaghavendra G <rgowdapp@redhat.com>2016-11-21 23:01:18 -0800
commit25817a8c868b6c1b8149117f13e4216a99e453aa (patch)
treefe42ae33a20de76c7e5022c479a7a026268c6c55 /extras/run-gluster.tmpfiles.in
parent3e405b546e8b9fe15ae477613474e9cd2d2df4e7 (diff)
performance/io-threads: Exit threads in fini() as well
Problem: io-threads starts the thread in 'init()' but doesn't clean them up on 'fini()'. It relies on PARENT_DOWN to exit threads but there can be cases where event before PARENT_UP the graph init code can think of issuing fini(). This code path is hit when glfs_init() is called on a volume that is in 'stopped' state. It leads to a crash in ganesha process, because the io-thread tries to access freed memory. Fix: Ideal fix would be to wait for all fops in io-thread list to be completed on PARENT_DOWN, and have fini() do cleanup of threads. Because there is no proper documentation about how PARENT_DOWN/fini are supposed to be used, we are getting different kinds of sequences in different higher level protocols. So for now cleaning up in both PARENT_DOWN and fini(). Fuse doesn't call fini() gfapi is not calling PARENT_DOWN in some cases, so for now I don't see another way out. BUG: 1396793 Change-Id: I9c9154e7d57198dbaff0f30d3ffc25f6d8088aec Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/15888 Smoke: Gluster Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Diffstat (limited to 'extras/run-gluster.tmpfiles.in')
0 files changed, 0 insertions, 0 deletions