From: Martin Wilck <mwilck@suse.com>
To: Benjamin Marzinski <bmarzins@redhat.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH v3 04/19] libmultipath: cleanup tur locking
Date: Mon, 01 Oct 2018 23:08:00 +0200 [thread overview]
Message-ID: <6fb36b656763e0231ac0f7ec1298e6879eda23ce.camel@suse.com> (raw)
In-Reply-To: <1537571127-10143-5-git-send-email-bmarzins@redhat.com>
On Fri, 2018-09-21 at 18:05 -0500, Benjamin Marzinski wrote:
> There are only three variables whose access needs to be synchronized
> between the tur thread and the path checker itself: state, message,
> and
> active. The rest of the variables are either only written when the
> tur
> thread isn't running, or they aren't accessed by the tur thread, or
> they
> are atomics that are themselves used to synchronize things.
>
> This patch limits the amount of code that is covered by ct->lock to
> only what needs to be locked. It also makes ct->lock no longer a
> recursive lock. To make this simpler, tur_thread now only sets the
> state and message one time, instead of twice, since PATH_UNCHECKED
> was never able to be returned anyway.
>
> One benefit of this is that the tur checker thread gets more time to
> call tur_check() and return before libcheck_check() gives up and
> return PATH_PENDING.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Reviewed-by: Martin Wilck <mwilck@suse.com>
> ---
> libmultipath/checkers/tur.c | 49 ++++++++++++++++++-----------------
> ----------
> 1 file changed, 20 insertions(+), 29 deletions(-)
>
> diff --git a/libmultipath/checkers/tur.c
> b/libmultipath/checkers/tur.c
> index abda162..9f6ef51 100644
> --- a/libmultipath/checkers/tur.c
> +++ b/libmultipath/checkers/tur.c
> @@ -53,7 +53,6 @@ struct tur_checker_context {
> int libcheck_init (struct checker * c)
> {
> struct tur_checker_context *ct;
> - pthread_mutexattr_t attr;
> struct stat sb;
>
> ct = malloc(sizeof(struct tur_checker_context));
> @@ -65,10 +64,7 @@ int libcheck_init (struct checker * c)
> ct->fd = -1;
> uatomic_set(&ct->holders, 1);
> pthread_cond_init_mono(&ct->active);
> - pthread_mutexattr_init(&attr);
> - pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
> - pthread_mutex_init(&ct->lock, &attr);
> - pthread_mutexattr_destroy(&attr);
> + pthread_mutex_init(&ct->lock, NULL);
> if (fstat(c->fd, &sb) == 0)
> snprintf(ct->devt, sizeof(ct->devt), "%d:%d",
> major(sb.st_rdev),
> minor(sb.st_rdev));
> @@ -213,12 +209,6 @@ static void *tur_thread(void *ctx)
>
> condlog(3, "%s: tur checker starting up", ct->devt);
>
> - /* TUR checker start up */
> - pthread_mutex_lock(&ct->lock);
> - ct->state = PATH_PENDING;
> - ct->message[0] = '\0';
> - pthread_mutex_unlock(&ct->lock);
> -
> state = tur_check(ct->fd, ct->timeout, msg);
> pthread_testcancel();
>
> @@ -283,13 +273,6 @@ int libcheck_check(struct checker * c)
> /*
> * Async mode
> */
> - r = pthread_mutex_lock(&ct->lock);
> - if (r != 0) {
> - condlog(2, "%s: tur mutex lock failed with %d", ct-
> >devt, r);
> - MSG(c, MSG_TUR_FAILED);
> - return PATH_WILD;
> - }
> -
> if (ct->thread) {
> if (tur_check_async_timeout(c)) {
> int running = uatomic_xchg(&ct->running, 0);
> @@ -305,23 +288,29 @@ int libcheck_check(struct checker * c)
> } else {
> /* TUR checker done */
> ct->thread = 0;
> + pthread_mutex_lock(&ct->lock);
> tur_status = ct->state;
> strlcpy(c->message, ct->message, sizeof(c-
> >message));
> + pthread_mutex_unlock(&ct->lock);
> }
> - pthread_mutex_unlock(&ct->lock);
> } else {
> if (uatomic_read(&ct->holders) > 1) {
> /* pthread cancel failed. If it didn't get the
> path
> state already, timeout */
> - if (ct->state == PATH_PENDING) {
> - pthread_mutex_unlock(&ct->lock);
> + pthread_mutex_lock(&ct->lock);
> + tur_status = ct->state;
> + pthread_mutex_unlock(&ct->lock);
> + if (tur_status == PATH_PENDING) {
> condlog(3, "%s: tur thread not
> responding",
> ct->devt);
> return PATH_TIMEOUT;
> }
> }
> /* Start new TUR checker */
> - ct->state = PATH_UNCHECKED;
> + pthread_mutex_lock(&ct->lock);
> + tur_status = ct->state = PATH_PENDING;
> + ct->message[0] = '\0';
> + pthread_mutex_unlock(&ct->lock);
> ct->fd = c->fd;
> ct->timeout = c->timeout;
> uatomic_add(&ct->holders, 1);
> @@ -334,20 +323,22 @@ int libcheck_check(struct checker * c)
> uatomic_sub(&ct->holders, 1);
> uatomic_set(&ct->running, 0);
> ct->thread = 0;
> - pthread_mutex_unlock(&ct->lock);
> condlog(3, "%s: failed to start tur thread,
> using"
> " sync mode", ct->devt);
> return tur_check(c->fd, c->timeout, c-
> >message);
> }
> tur_timeout(&tsp);
> - r = pthread_cond_timedwait(&ct->active, &ct->lock,
> &tsp);
> - tur_status = ct->state;
> - strlcpy(c->message, ct->message, sizeof(c->message));
> + pthread_mutex_lock(&ct->lock);
> + if (ct->state == PATH_PENDING)
> + r = pthread_cond_timedwait(&ct->active, &ct-
> >lock,
> + &tsp);
> + if (!r) {
> + tur_status = ct->state;
> + strlcpy(c->message, ct->message, sizeof(c-
> >message));
> + }
> pthread_mutex_unlock(&ct->lock);
> - if (uatomic_read(&ct->running) != 0 &&
> - (tur_status == PATH_PENDING || tur_status ==
> PATH_UNCHECKED)) {
> + if (tur_status == PATH_PENDING) {
> condlog(3, "%s: tur checker still running", ct-
> >devt);
> - tur_status = PATH_PENDING;
> } else {
> int running = uatomic_xchg(&ct->running, 0);
> if (running)
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-10-01 21:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 23:05 [PATCH v3 00/19] Misc Multipath patches Benjamin Marzinski
2018-09-21 23:05 ` [PATCH v3 01/19] libmultipath: fix tur checker timeout Benjamin Marzinski
2018-10-01 19:51 ` Martin Wilck
2018-10-04 16:31 ` Benjamin Marzinski
2018-10-05 10:11 ` Martin Wilck
2018-10-05 17:02 ` Benjamin Marzinski
2018-10-05 19:23 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 02/19] libmultipath: fix tur checker double locking Benjamin Marzinski
2018-10-01 20:09 ` Martin Wilck
2018-10-01 20:44 ` Martin Wilck
2018-10-04 16:47 ` Benjamin Marzinski
2018-10-04 16:45 ` Benjamin Marzinski
2018-10-05 10:25 ` Martin Wilck
2018-10-05 17:10 ` Benjamin Marzinski
2018-10-05 19:07 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 03/19] libmultipath: fix tur memory misuse Benjamin Marzinski
2018-10-01 20:59 ` Martin Wilck
2018-10-02 7:48 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 04/19] libmultipath: cleanup tur locking Benjamin Marzinski
2018-10-01 21:08 ` Martin Wilck [this message]
2018-09-21 23:05 ` [PATCH v3 05/19] libmultipath: fix tur checker timeout issue Benjamin Marzinski
2018-10-01 21:09 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 06/19] libmultipath: fix set_int error path Benjamin Marzinski
2018-10-01 21:17 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 07/19] libmultipath: fix length issues in get_vpd_sgio Benjamin Marzinski
2018-10-01 21:25 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 08/19] libmultipath: _install_keyword cleanup Benjamin Marzinski
2018-10-01 21:26 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 09/19] libmultipath: remove unused code Benjamin Marzinski
2018-10-01 21:28 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 10/19] libmultipath: fix memory issue in path_latency prio Benjamin Marzinski
2018-10-01 21:30 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 11/19] libmultipath: fix null dereference int alloc_path_group Benjamin Marzinski
2018-10-01 21:33 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 12/19] libmutipath: don't use malformed uevents Benjamin Marzinski
2018-10-01 21:31 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 13/19] multipath: fix max array size in print_cmd_valid Benjamin Marzinski
2018-10-01 21:35 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 14/19] multipathd: function return value tweaks Benjamin Marzinski
2018-10-01 21:37 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 15/19] multipathd: minor fixes Benjamin Marzinski
2018-10-01 21:38 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 16/19] multipathd: remove useless check and fix format Benjamin Marzinski
2018-10-01 21:40 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 17/19] multipathd: fix memory leak on error in configure Benjamin Marzinski
2018-10-01 21:42 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 18/19] libmultipath: Don't blank intialized paths Benjamin Marzinski
2018-10-01 22:00 ` Martin Wilck
2018-10-02 22:37 ` Martin Wilck
2018-10-05 19:38 ` Benjamin Marzinski
2018-10-08 9:41 ` Martin Wilck
2018-10-09 22:20 ` Benjamin Marzinski
2018-10-08 9:35 ` Martin Wilck
2018-09-21 23:05 ` [PATCH v3 19/19] libmultipath: Fixup updating paths Benjamin Marzinski
2018-10-01 22:30 ` Martin Wilck
2018-10-05 20:32 ` Benjamin Marzinski
2018-10-07 8:36 ` [PATCH v3 00/19] Misc Multipath patches Christophe Varoqui
2018-10-09 16:13 ` Benjamin Marzinski
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=6fb36b656763e0231ac0f7ec1298e6879eda23ce.camel@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.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