Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Dec 2006 16:41:36 +0300
From:      Andrey Chernov <ache@FreeBSD.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        current@FreeBSD.org
Subject:   Re: sysv_ipc.c broken in v1.30 (was Re: sysvshm appearse broken in -current)
Message-ID:  <20061216134136.GB1754@nagual.pp.ru>
In-Reply-To: <20061216131715.C72986@fledge.watson.org>
References:  <20061216055903.GA2712@nagual.pp.ru> <20061216111656.GA7501@nagual.pp.ru> <20061216112117.P72986@fledge.watson.org> <20061216114426.GA7735@nagual.pp.ru> <20061216120746.E72986@fledge.watson.org> <20061216125136.GA1094@nagual.pp.ru> <20061216125419.J72986@fledge.watson.org> <20061216131135.GA1393@nagual.pp.ru> <20061216131715.C72986@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 16, 2006 at 01:24:59PM +0000, Robert Watson wrote:
> control implementation is structured.  A bug in the new ipcperm() may well 
> be triggering the appearance of the error, but it appears also to be a 
> product of incorrectly structured code in the existing shared memory 
> implementation. The long-term goal is to have a correct implementation of 
> the new code, not simply revert to the old code.

Well, in case t-shm tests will pass, any re-structuring will be fine 
for me.

> >>failure. It could be that both a bug in ipcperm() and a big in shmget()
> >
> >I'll try to make ktrace output, a bit later.
> 
> That's not what I asked for.

In that case I'll be delayed for a longer time - right now -current is not 
bootable - fatal trap due to kmacy@ changes.

-- 
http://ache.pp.ru/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061216134136.GB1754>