From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:26:55 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 CD78916A400 for ; Mon, 3 Apr 2006 03:26:55 +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 B357843D45 for ; Mon, 3 Apr 2006 03:26:54 +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 k333Qq65027572; Sun, 2 Apr 2006 23:26:52 -0400 (EDT) To: Kris Kennaway In-reply-to: <20060403032130.GA58053@xor.obsecurity.org> References: <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> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Sun, 02 Apr 2006 23:21:30 -0400" Date: Sun, 02 Apr 2006 23:26:52 -0400 Message-ID: <27571.1144034812@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:26:55 -0000 Kris Kennaway writes: > On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: >> 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. > By default SysV shared memory is disallowed in jails. Hm, the present problem seems to be about semaphores not shared memory ... although I'd not be surprised to find that there's a similar issue around shared memory. Anyway, if FBSD's position is that they are uninterested in supporting SysV IPC in connection with jails, then I think the Postgres project position has to be that we are uninterested in supporting Postgres inside FBSD jails. Sorry Marc :-( regards, tom lane