diff options
author | Raghavendra Bhat <raghavendra@redhat.com> | 2019-04-15 14:09:34 -0400 |
---|---|---|
committer | Amar Tumballi <amarts@redhat.com> | 2019-04-17 03:27:24 +0000 |
commit | b922793588ad23a9b12ce65abd29e8f45ac87998 (patch) | |
tree | dd60c0e9a3b99846c94ed0dd2aaad6d7dad66255 /COMMITMENT | |
parent | e5ff6cc397e7a23dff4024efb6806cb004a89ee6 (diff) |
features/bit-rot-stub: clean the mutex after cancelling the signer thread
When bit-rot feature is disabled, the signer thread from the bit-rot-stub
xlator (the thread which performs the setxattr of the signature on to the
disk) is cancelled. But, if the cancelled signer thread had already held
the mutex (&priv->lock) which it uses to monitor the queue of files to
be signed, then the mutex is never released. This creates problems in
future when the feature is enabled again. Both the new instance of the
signer thread and the regular thread which enqueues the files to be
signed will be blocked on this mutex.
So, as part of cancelling the signer thread, unlock the mutex associated
with it as well using pthread_cleanup_push and pthread_cleanup_pop.
Change-Id: Ib761910caed90b268e69794ddeb108165487af40
updates: bz#1700078
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'COMMITMENT')
0 files changed, 0 insertions, 0 deletions