From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:17:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 719BE16A400 for ; Mon, 3 Apr 2006 03:17:52 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60EC043D6E for ; Mon, 3 Apr 2006 03:17:51 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k333HngA027516; Sun, 2 Apr 2006 23:17:49 -0400 (EDT) To: Kris Kennaway In-reply-to: <20060403031157.GA57914@xor.obsecurity.org> References: <26524.1144026385@sss.pgh.pa.us> <20060402222843.X947@ganymede.hub.org> <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Sun, 02 Apr 2006 23:11:57 -0400" Date: Sun, 02 Apr 2006 23:17:49 -0400 Message-ID: <27515.1144034269@sss.pgh.pa.us> From: Tom Lane Cc: "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 03:17:52 -0000 Kris Kennaway writes: > On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: >> If this is the story, then FBSD have broken their system and must revert >> their change. They do not have kernel behavior that totally hides the >> existence of the other process, and therefore having some calls that >> pretend it's not there is simply inconsistent. > I'm guessing it's a deliberate change to prevent the information > leakage between jails. I have no objection to doing that, so long as you are actually doing it correctly. This example shows that each jail must have its own SysV semaphore key space, else information leaks anyway. The current situation breaks Postgres, and therefore I suggest reverting the errno change until you are prepared to fix the SysV IPC stuff to be per-jail. regards, tom lane