Date: Wed, 7 Aug 2019 01:06:46 -0400 From: Daniel Eischen <deischen@freebsd.org> To: Erich Dollansky <freebsd.ed.lists@sumeritec.com> Cc: freebsd-questions@freebsd.org, freebsd-threads@freebsd.org Subject: Re: mutex held in a thread which is cancelled stays busy Message-ID: <9AA32154-7A31-45E1-A354-3AA6A67D67AD@freebsd.org> In-Reply-To: <20190807120734.1c55392d.freebsd.ed.lists@sumeritec.com> References: <20190806165429.14bc4052.freebsd.ed.lists@sumeritec.com> <1FC05CEB-982F-484F-9E41-5A74FF564494@freebsd.org> <20190807095521.23e79874.freebsd.ed.lists@sumeritec.com> <0CEB9578-74BE-42E7-A612-9A7AE3DBD052@freebsd.org> <20190807120734.1c55392d.freebsd.ed.lists@sumeritec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 7, 2019, at 12:07 AM, Erich Dollansky <freebsd.ed.lists@sumeritec.c= om> wrote: >=20 > Hi, >=20 > On Tue, 6 Aug 2019 23:38:51 -0400 > Daniel Eischen <deischen@freebsd.org> wrote: >>=20 >> Yes, I believe so. I'm curious if the bug also exists in -current. >>=20 > I do not have CURRENT on any machine at the moment. I can try it tomorrow. I can come up with my own test for it, but it would b= e easier if you could send me (privately, if you want) the one you've alread= y got. -- DE=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9AA32154-7A31-45E1-A354-3AA6A67D67AD>