[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: PR/53998 CVS commit: src/sys/kern
The following reply was made to PR kern/53998; it has been noted by GNATS.
From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
Subject: Re: PR/53998 CVS commit: src/sys/kern
Date: Mon, 25 Feb 2019 09:22:40 -0500
On Feb 25, 2:05pm, joel.bertrand%systella.fr@localhost (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
-- Subject: Re: PR/53998 CVS commit: src/sys/kern
| I have applied bith patch (you will find in attachment patch against -8).
| This patch partially fixes this PR as my test program can create more
| threads before first sem_init() failure. But I think there is another
| race condition somewhere in semaphore subsystem.
| After sem_init() failure, there is no specific message in dmesg or logfile.
| I don't understand why atomic_dec_uint(&nsems_total) or
| atomic_inc_uint(&nsems_total) are not protected by a lock.
Yes, the whole thing is racy... But atomics don't need to be protected
by locks... How does it fail now ENFILE?
Main Index |
Thread Index |