From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Van Assche Subject: Re: [PATCH 0/7] multipathd: Fix race conditions related to thread termination Date: Mon, 15 Aug 2016 08:29:18 -0700 Message-ID: References: <31d43b64-36c8-1a24-a849-230b5cf6323c@sandisk.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <31d43b64-36c8-1a24-a849-230b5cf6323c@sandisk.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Christophe Varoqui Cc: device-mapper development List-Id: dm-devel.ids 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.