From owner-freebsd-hackers Tue Apr 24 5: 7:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from green.bikeshed.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 410C237B42C for ; Tue, 24 Apr 2001 05:07:16 -0700 (PDT) (envelope-from green@green.bikeshed.org) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.2/8.11.1) with ESMTP id f3OC7F159738 for ; Tue, 24 Apr 2001 08:07:15 -0400 (EDT) (envelope-from green@green.bikeshed.org) Message-Id: <200104241207.f3OC7F159738@green.bikeshed.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: hackers@FreeBSD.org Subject: Anyone know of RFMEM vm/sysv_shm.c-related races? From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Apr 2001 08:07:14 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some way, using Linux LinuxThreads programs that use shared memory, I've ended up with dozens of shared memory segments that reportedly still have 1 attachment (which I'm really darn certain is impossible since I've killed _everything_ in sight). I think something must have happened that for some reason shmexit() was not called on process exit, vm_shm refcnt was increased too many times, vm_shm refcnt was not decreased enough times... whatever the case, there may be an old vmspace just floating around stranded, or just a simple bug with vm_shm... Does anyone have any clues about races or weird issues in this area? It's pretty exasperating to not be able to figure this one out. I don't immediately see any obvious races after half an hour of searching (since it appears all calls that can modify vmspace directly require Giant being held). -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message