From: Hannes Reinecke <hare@suse.de>
To: Martin Wilck <mwilck@suse.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
Guan Junxiong <guanjunxiong@huawei.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH v2 1/2] libmultipath: fix race in stop_io_err_stat_thread
Date: Wed, 7 Mar 2018 08:23:47 +0100 [thread overview]
Message-ID: <2de3d65f-dea5-a8d3-9738-23ae90c79bda@suse.de> (raw)
In-Reply-To: <20180306211842.2556-1-mwilck@suse.com>
On 03/06/2018 10:18 PM, Martin Wilck wrote:
> It's wrong, and unnecessary, to call pthread_kill after
> pthread_cancel. I have observed cases where the io_err checker
> thread hung in libpthread after receiving the USR2 signal, in particular
> when multipathd is run under strace. (If multipathd is killed with
> SIGINT under strace, and the io_error thread is running, it happens
> almost every time). If this happens, the io_err thread
> tries to obtain a mutex in the urcu code (presumably rcu_unregister_thread())
> and the main thread hangs in pthread_join().
>
> With the change from this patch, the thread is shut down cleanly. I haven't
> observed the hang under strace with the patch.
>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
> ---
> libmultipath/io_err_stat.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/libmultipath/io_err_stat.c b/libmultipath/io_err_stat.c
> index 00bac9e0e755..536ba87968fd 100644
> --- a/libmultipath/io_err_stat.c
> +++ b/libmultipath/io_err_stat.c
> @@ -749,7 +749,6 @@ destroy_ctx:
> void stop_io_err_stat_thread(void)
> {
> pthread_cancel(io_err_stat_thr);
> - pthread_kill(io_err_stat_thr, SIGUSR2);
> pthread_join(io_err_stat_thr, NULL);
> free_io_err_pathvec(paths);
> io_destroy(ioctx);
>
Good point.
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2018-03-07 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180306211842.2556-1-mwilck@suse.com>
2018-03-06 21:18 ` [PATCH v2 2/2] multipathd: start marginal path checker thread lazily Martin Wilck
2018-03-07 7:25 ` Hannes Reinecke
2018-03-07 7:23 ` Hannes Reinecke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2de3d65f-dea5-a8d3-9738-23ae90c79bda@suse.de \
--to=hare@suse.de \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=guanjunxiong@huawei.com \
--cc=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox