From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id CA8CB4696C3 for ; Wed, 22 Apr 2020 18:36:09 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id y4so2781259ljn.7 for ; Wed, 22 Apr 2020 08:36:09 -0700 (PDT) Date: Wed, 22 Apr 2020 18:36:06 +0300 From: Cyrill Gorcunov Message-ID: <20200422153606.GB3072@uranus> References: <41a1decbbad25ee4b080052e64f65d1c4206c426.1587490798.git.lvasiliev@tarantool.org> <20200422142046.GA3072@uranus> <1ba0a66e-e252-99d7-5eb9-b5d5fbe8f95e@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1ba0a66e-e252-99d7-5eb9-b5d5fbe8f95e@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] Add a check whether glibc is used List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: lvasiliev Cc: tarantool-patches@dev.tarantool.org On Wed, Apr 22, 2020 at 05:52:18PM +0300, lvasiliev wrote: > Comment from code of cbus_hang test: > " We want to cancel canceled thread in the moment of cpipe_flush_cb > will be processing. > A Linux specific dirty hack will be used for reproduce the bug. > We need to synchronize the main thread and the canceled worker thread. > So, do it using the endpoint's mutex internal field(__data.__lock)." > "A Linux specific" - a glibc specific. Aha! So it is test's specific. Pleas add this into changelog itself. Reviewed-by: Cyrill Gorcunov