All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 0/7] multipathd: Fix race conditions related to thread termination
Date: Mon, 15 Aug 2016 08:29:18 -0700	[thread overview]
Message-ID: <d71738e7-4909-fb4d-8bc7-372035f7f161@sandisk.com> (raw)
In-Reply-To: <31d43b64-36c8-1a24-a849-230b5cf6323c@sandisk.com>

On 08/15/2016 08:24 AM, Bart Van Assche wrote:
> As you may already have noticed the code in multipathd for terminating
> worker threads triggers several race conditions. It would be appreciated
> if you could review and/or apply the following seven patches that fix
> these race conditions:
>
> 0001-multipathd-fix-memory-allocation-logic-error-for-pol.patch
> 0002-libmultipath-Remove-a-data-structure-that-has-been-c.patch
> 0003-libmultipath-Remove-debugging-code-from-lock.h.patch
> 0004-libmultipath-Convert-lock-and-unlock-into-inline-fun.patch
> 0005-libmultipath-Inline-mutex-in-struct-mutex_lock.patch
> 0006-libmultipath-Introduce-timedlock.patch
> 0007-multipathd-Remove-a-busy-waiting-loop.patch

(replying to my own e-mail)

A correction: this series consists of 6 patches instead of 7.

Bart.

  parent reply	other threads:[~2016-08-15 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 15:24 [PATCH 0/7] multipathd: Fix race conditions related to thread termination Bart Van Assche
2016-08-15 15:25 ` [PATCH 1/6] libmultipath: Remove a data structure that has been commented out Bart Van Assche
2016-08-15 15:26 ` [PATCH 2/6] libmultipath: Remove debugging code from lock.h Bart Van Assche
2016-08-15 15:26 ` [PATCH 3/6] libmultipath: Convert lock() and unlock() into inline functions Bart Van Assche
2016-08-15 15:27 ` [PATCH 4/6] libmultipath: Inline mutex in struct mutex_lock Bart Van Assche
2016-08-15 15:27 ` [PATCH 5/6] libmultipath: Introduce timedlock() Bart Van Assche
2016-08-15 15:28 ` [PATCH 6/6] multipathd: Remove a busy-waiting loop Bart Van Assche
2016-08-16  6:31   ` Hannes Reinecke
2016-08-16 20:11     ` Bart Van Assche
2016-08-17 14:44       ` Hannes Reinecke
2016-08-17 15:37         ` Bart Van Assche
2016-08-17 19:42       ` Dragan Stancevic
2016-08-17 19:55         ` Bart Van Assche
2016-08-25  3:33     ` Benjamin Marzinski
2016-08-26 14:04       ` Hannes Reinecke
2016-08-17 19:36   ` Dragan Stancevic
2016-08-17 19:57     ` Bart Van Assche
2016-08-18 20:54       ` Dragan Stancevic
2016-08-18 22:42         ` Bart Van Assche
2016-08-15 15:29 ` Bart Van Assche [this message]
2016-08-16  7:38   ` [PATCH 0/7] multipathd: Fix race conditions related to thread termination Christophe Varoqui

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=d71738e7-4909-fb4d-8bc7-372035f7f161@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=christophe.varoqui@opensvc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.