From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Guan Junxiong <guanjunxiong@huawei.com>
Cc: dm-devel@redhat.com, Martin Wilck <mwilck@suse.com>
Subject: [PATCH v3 0/2] marginal path fixes
Date: Wed, 7 Mar 2018 15:07:31 +0100 [thread overview]
Message-ID: <20180307140733.28709-1-mwilck@suse.com> (raw)
Changes wrt v2:
- 2/2: Fixed bug that would cause a crash if marginal path checker was off.
(if we don't start the thread, we'd better not kill it, either).
Martin Wilck (2):
libmultipath: fix race in stop_io_err_stat_thread
multipathd: start marginal path checker thread lazily
libmultipath/configure.c | 14 ++++++++---
libmultipath/configure.h | 3 ++-
libmultipath/io_err_stat.c | 59 ++++++++++++++++++++++++++++++++++++++++++----
libmultipath/structs_vec.c | 3 ++-
multipathd/cli_handlers.c | 2 +-
multipathd/main.c | 8 ++-----
6 files changed, 72 insertions(+), 17 deletions(-)
--
2.16.1
next reply other threads:[~2018-03-07 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 14:07 Martin Wilck [this message]
2018-03-07 14:07 ` [PATCH v3 1/2] libmultipath: fix race in stop_io_err_stat_thread Martin Wilck
2018-03-07 14:07 ` [PATCH v3 2/2] multipathd: start marginal path checker thread lazily Martin Wilck
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=20180307140733.28709-1-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=guanjunxiong@huawei.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