Date: Thu, 11 Feb 1999 12:38:12 +1100 From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au> To: dillon@apollo.backplane.com, tlambert@primenet.com Cc: hackers@FreeBSD.ORG Subject: Re: portability of shm, mmap, pipes and socket IPC Message-ID: <99Feb11.122748est.40371@border.alcanet.com.au>
next in thread | raw e-mail | index | archive | help
Terry Lambert <tlambert@primenet.com> wrote: >FreeBSD semaphores are inadequately resource tracked in _exit(). Matthew Dillon <dillon@apollo.backplane.com> wrote: > All semaphores are inadequately resource tracked in _exit(), it's a > problem inherited from the SYSV implementation. Could someone please describe what the problem(s) are and what impact they have on applications using SysV semaphores. I have an application (running on 3.0-RELEASE) that relies on the kernel correctly tracking SEM_UNDO's. (Basically I have a wrapper that seizes a semaphore with sem_op = -1, sem_flg = SEM_UNDO and then execs a process that knows nothing about the semaphores.) I was seeing some wierd behaviour, but I thought that was a (now fixed) bug in the kernel handling of SEMUME and SEMUSZ (see PR kern/9068). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Feb11.122748est.40371>