From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvMsojiVpw7S for ; Wed, 17 Aug 2011 14:17:43 +0200 (CEST) Received: from molly.corsac.net (molly.corsac.net [IPv6:2002:4ec0:442e::1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 17 Aug 2011 14:17:43 +0200 (CEST) Received: from [192.168.24.20] (plateformev6-124-46.pck.nerim.net [62.212.124.46]) by molly.corsac.net (Postfix) with ESMTPSA id 9B0B582D3B for ; Wed, 17 Aug 2011 14:17:27 +0200 (CEST) From: Yves-Alexis Perez In-Reply-To: <4E4BA673.9060000@redhat.com> References: <4E4AD6F2.8020800@archlinux.org> <4E4AE4DB.30205@redhat.com> <4E4AE740.9020800@archlinux.org> <4E4B6E61.4020301@redhat.com> <4E4BA46F.5010809@alexanderkoch.net> <1313577794.6534.12.camel@oban> <4E4B9C78.70504@redhat.com> <4E4BA673.9060000@redhat.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 17 Aug 2011 14:17:40 +0200 Message-ID: <1313583460.6534.14.camel@oban> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for cookie 0xdeadbeef: incorrect semaphore state List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On mer., 2011-08-17 at 13:30 +0200, Milan Broz wrote: > On 08/17/2011 12:48 PM, Milan Broz wrote: > >> For chromium, it might be that the default sandboxing (setuid one) > uses > >> PID and network namespaces. Not sure why it'd mess with semaphores, > but > >> maybe there's something to look at there. > > It is apparently related to sandboxing, namely to using namespaces > (You need kernel support for it to reproduce. See about:sandbox in > chromium.) > > I would really like to know what crazy is chromium doing to global > system. > > Despite I like the idea of sandboxing I have to ask > why it is part of "browser" and not some separate package. > What's next? Bundled kernel? :) Because each tab is sandboxed. There's a seccomp sandbox available too. > > Also installing setuid /usr/lib64/chromium/chromium-sandbox ... > Not even man page for it. Sigh... See http://code.google.com/p/chromium/wiki/LinuxSandboxing -- Yves-Alexis