<div dir="ltr">Applied.<div>Thanks.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 15, 2016 at 5:29 PM, Bart Van Assche <span dir="ltr"><<a href="mailto:bart.vanassche@sandisk.com" target="_blank">bart.vanassche@sandisk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 08/15/2016 08:24 AM, Bart Van Assche wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As you may already have noticed the code in multipathd for terminating<br>
worker threads triggers several race conditions. It would be appreciated<br>
if you could review and/or apply the following seven patches that fix<br>
these race conditions:<br>
<br>
0001-multipathd-fix-memory-all<wbr>ocation-logic-error-for-pol.<wbr>patch<br>
0002-libmultipath-Remove-a-dat<wbr>a-structure-that-has-been-c.<wbr>patch<br>
0003-libmultipath-Remove-debug<wbr>ging-code-from-lock.h.patch<br>
0004-libmultipath-Convert-lock<wbr>-and-unlock-into-inline-fun.<wbr>patch<br>
0005-libmultipath-Inline-mutex<wbr>-in-struct-mutex_lock.patch<br>
0006-libmultipath-Introduce-ti<wbr>medlock.patch<br>
0007-multipathd-Remove-a-busy-<wbr>waiting-loop.patch<br>
</blockquote>
<br></span>
(replying to my own e-mail)<br>
<br>
A correction: this series consists of 6 patches instead of 7.<span class="HOEnZb"><font color="#888888"><br>
<br>
Bart.<br>
</font></span></blockquote></div><br></div>