[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 0/2] qemu-thread: Strict unlock check
|
From: |
Peter Xu |
|
Subject: |
Re: [PATCH RFC 0/2] qemu-thread: Strict unlock check |
|
Date: |
Thu, 13 Oct 2022 11:05:38 -0400 |
On Thu, Oct 13, 2022 at 11:31:20AM +0100, Peter Maydell wrote:
> We used to use PTHREAD_MUTEX_ERRORCHECK, but stopped because it
> does not work with the idiom we use for handling mutexes across
> fork() where you take the lock in the parent, and then unlock it
> in the child after the fork. With glibc's implementation of
> PTHREAD_MUTEX_ERRORCHECK the unlock in the child fails. See
> commit 24fa90499f8b24bcba29 from 2015.
Oops, thanks Peter.
--
Peter Xu