Date: Sun, 17 Dec 2006 18:39:14 +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: <20061217153914.GA30048@nagual.pp.ru> In-Reply-To: <20061216125419.J72986@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 16, 2006 at 01:00:56PM +0000, Robert Watson wrote: > As I said, this is something that I hope to revisit in the next few days. > However, it would be helpful if you could tell me the arguments and call > path to the ipcperm() function instance that's generating the improper > failure. It could be that both a bug in ipcperm() and a big in shmget() This is kernel debug running test from t-shm.c which fails (from root). Is it what you need? acc_mode 0x1b0 owner obj_mode 0x9b0 dac_granted 0x1180 priv_granted 0x0 EACCES -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061217153914.GA30048>