From owner-freebsd-threads@freebsd.org Wed Aug 7 01:56:25 2019 Return-Path: Delivered-To: freebsd-threads@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C908EBA8A2 for ; Wed, 7 Aug 2019 01:56:25 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out2-4.antispamcloud.com (out2-4.antispamcloud.com [185.201.17.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 463F3X5Zyzz440q for ; Wed, 7 Aug 2019 01:56:24 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from srv31.niagahoster.com ([153.92.8.106]) by mx120.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1hvBBa-0012Ab-6f for freebsd-threads@freebsd.org; Wed, 07 Aug 2019 03:56:22 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=1e78t4imKpgUmFxG2B5GuLtxc9x7+/NJa3kdb6vDPt0=; b=rF7ysYRbs9NaWWAuMIgra2Ruky 2e08kZcEEgBumv7P5guLigAa5fBPCaZPBBblyZUul4iYUy4IQeY765vSoU+kFSSoH1tqat9jxTgO9 TqumBBWORMmPY5SVgnIbxDFyLTSMGOXQ06fqQcdpHprxzhoyY7vTkrAbm41xCX59yI3H2QZBIP8aV vcn73HnbIec5BN0oonJwMKTlyBIWU1XYqFqaXyzNKitqPQiHz6zc3xuKW5guu++rYXLeSH3qLxsrU MyDw/oqxZiEW9viio0pOT/JRIEPV5gGM8pNKidZWvfJW5SAlZ4wnqOMt8k7NkTR9EPDBejsAiBpbB Zgum7jkg==; Received: from [114.125.104.25] (port=40395 helo=Ryzen1.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1hvBAh-0009xs-F4; Wed, 07 Aug 2019 08:55:29 +0700 Date: Wed, 7 Aug 2019 09:55:21 +0800 From: Erich Dollansky To: Daniel Eischen Cc: freebsd-threads@freebsd.org, freebsd-questions@freebsd.org Subject: Re: mutex held in a thread which is cancelled stays busy Message-ID: <20190807095521.23e79874.freebsd.ed.lists@sumeritec.com> In-Reply-To: <1FC05CEB-982F-484F-9E41-5A74FF564494@freebsd.org> References: <20190806165429.14bc4052.freebsd.ed.lists@sumeritec.com> <1FC05CEB-982F-484F-9E41-5A74FF564494@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-Spampanel-Domain: out.niagahoster.com X-Spampanel-Username: niaga X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.10) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0YiRRkpbHZ8F3zevhEShTfypSDasLI4SayDByyq9LIhVcXSMTL9HkUMo SGLCNdCGjkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDfcKM/QcQW5M3f6M90DU6mLNt WyfKuzLBS5jlSy+O1N0BcORxfCojcTOpEjtvWHp2IJb1FKLNsjvUSqjLKZkTrTg9YkzbMy6DOYhG 3MUcvhoC5E0fa4xMuNxWhNGpgfrZzHsFnNV2ytQnVONhlZaGFBQA8Ado50lIXu9sNo8pO8kLVwl4 MD27u7ynKZb4TqTDVgW9/bktU41htiJ8fk7NkDAVHjYntR9elzPavaRCwERBjtYFPuVXfsT0ihIB NX8lghGR310uTa9T9T94Qx6UuKB7SU5M7j/zBp6iK1Co5/LyvYF41YKwtUHAIHcwkMwUd8hF8H+X RkeFFoCQxNYyp7turLxlLrVurcLqU0q1kASi6hr1FOEGhgodHuT0F3kfSxjK/EpQH87O+fXsIADf 6/e92HUiJHLkzIMeCG+jIafPY7UumbsOejcyeB6AGynhLYxG0axR7xEpzKsyxrpVaLTlo0e71UIn awUsVFFOlV/74O4hBSz/kkmPgL+fgIguSMbKk2e9G11Azr3iStcENdj9x4PWT7trWXGgMYrgWnHK axDVS0vdsIXmmT90wb1xwxqeeDDmjLCnpQf6ku5kW1BCtQF/9CBw4y9jfRtIAhTglGrdRgcS3bYi 8gwoFJOVb1gnp9htNUCeH1MEeKnWYzYAP276cXp4qgQynS/ujBk14O9uIBc4R2FHvu2iptL1u3Q2 fQqqrKGeyubQR9K7jU4vidrAbzPztKfs4s5XguKm1K5iNA1wnmU4zGCXxM+PxIb2spKBkQqOaCyT p/d/hHLgPBUCbE0tM1sfNl2t8YqRNkAEETzgfODJrA65N8kZVm2lHuINJIGiJ73RKeuKpVaXv/21 ZIPO13utXt9B17khEWyJzIkwSFAW0Pw8uiKeA9a5xIXWLWP5TEF+bN/aB3VdM9QAgYnxkm3ga//4 ZxQQddh7BR1NngH8ZlFzSe+X X-Report-Abuse-To: spam@quarantine10.antispamcloud.com X-Rspamd-Queue-Id: 463F3X5Zyzz440q X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sumeritec.com header.s=default header.b=rF7ysYRb; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd.ed.lists@sumeritec.com has no SPF policy when checking 185.201.17.4) smtp.mailfrom=freebsd.ed.lists@sumeritec.com X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[sumeritec.com:s=default]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sumeritec.com]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[sumeritec.com:+]; NEURAL_HAM_SHORT(-0.85)[-0.852,0]; MID_CONTAINS_FROM(1.00)[]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[4.17.201.185.list.dnswl.org : 127.0.3.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:49544, ipnet:185.201.17.0/24, country:NL]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-0.44)[ipnet: 185.201.17.0/24(-1.87), asn: 49544(-0.33), country: NL(0.01)]; RECEIVED_SPAMHAUS_PBL(0.00)[25.104.125.114.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 01:56:25 -0000 Hi, On Tue, 6 Aug 2019 20:58:30 -0400 Daniel Eischen wrote: > > On Aug 6, 2019, at 4:54 AM, Erich Dollansky > > wrote: > > > > Hi, > > > > for testing purpose, I did the following. > > > > Start a thread, initialise a mutex in a global variable, lock the > > mutex and wait in that thread. > > > > Wait in the main program until above's thread waits and cancel it. > > > > Clean up behind the cancelled thread but leave intentional the mutex > > locked. > > > > I would have expected now to get an error like 'EOWNERDEAD' doing > > operations with that mutex. But I get 'EBUSY' as the error. > > Are you initializing the mutex as a robust mutex, via > pthread_mutexattr_setrobust()? Are you using _lock() or _trylock()? > > For _trylock(), you only get EOWNERDEAD for robust mutexes. It seems > that you should get EOWNERDEAD for _lock() in this case, so if that's > what you're doing, it sounds like it might be a bug. > I did both. One time with initialising the mutex with its defaults by handing over NULL as the attribute setting and one time with the attributes set. I use this line to set the attribute: pres = pthread_mutexattr_setrobust (& Attr, PTHREAD_MUTEX_ROBUST); The following line: pthread_mutexattr_getrobust (& Attr, &pres); Sets pres also to 1. I am doing this on 12.0-STABLE FreeBSD 12.0-STABLE r350391 GENERIC amd64 with the systems standard compiler. Is this the corrent way of doing it? Erich