diff options
| author | Mohammed Rafi KC <rkavunga@redhat.com> | 2019-05-11 22:40:22 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2019-05-31 11:27:37 +0000 |
| commit | e510f55bed6c26c6b995e7d9f3c35e1e4e482769 (patch) | |
| tree | e33a0fe5bba577eeeb37ed0631c1281369e12fde /tests/bugs/glusterd | |
| parent | f8b0ba06c4cea428f6eb7730f4430b3564c83da0 (diff) | |
glusterfsd/cleanup: Protect graph object under a lock
While processing a cleanup_and_exit function, we are
accessing a graph object. But this has not been protected
under a lock. Because a parallel cleanup of a graph is quite
possible which might lead to an invalid memory access
Change-Id: Id05ca70d5b57e172b0401d07b6a1f5386c044e79
fixes: bz#1708926
Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
Diffstat (limited to 'tests/bugs/glusterd')
| -rw-r--r-- | tests/bugs/glusterd/optimized-basic-testcases.t | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/tests/bugs/glusterd/optimized-basic-testcases.t b/tests/bugs/glusterd/optimized-basic-testcases.t index d700b5ed5af..110f1b92dae 100644 --- a/tests/bugs/glusterd/optimized-basic-testcases.t +++ b/tests/bugs/glusterd/optimized-basic-testcases.t @@ -289,7 +289,9 @@ mkdir -p /xyz/var/lib/glusterd/abc TEST $CLI volume create "test" $H0:/xyz/var/lib/glusterd/abc EXPECT 'Created' volinfo_field "test" 'Status'; -EXPECT "1" generate_statedump_and_check_for_glusterd_info +#While taking a statedump, there is a TRY_LOCK on call_frame, which might may cause +#failure. So Adding a EXPECT_WITHIN +EXPECT_WITHIN $PROCESS_UP_TIMEOUT "^1$" generate_statedump_and_check_for_glusterd_info cleanup_statedump `pidof glusterd` cleanup |