From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
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 PIMIbxsDWMYe for <dm-crypt@saout.de>;
 Thu, 10 Nov 2011 12:28:34 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 10 Nov 2011 12:28:34 +0100 (CET)
Message-ID: <4EBBB55E.2080902@redhat.com>
Date: Thu, 10 Nov 2011 12:28:30 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
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>
 <1313583460.6534.14.camel@oban> <4E4CD3CF.5050803@redhat.com>
 <4E4CE1B4.2070401@archlinux.org> <4E4CE8AB.9050106@redhat.com>
 <4E5242CE.2010108@archlinux.org> <4E537A8D.8020707@archlinux.org>
 <4E53945D.7060809@redhat.com> <j8uc5r$shm$1@dough.gmane.org>
In-Reply-To: <j8uc5r$shm$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for
 cookie 0xdeadbeef: incorrect semaphore state
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Sebastian Steinhuber <sebastian.steinhuber@googlemail.com>
Cc: dm-crypt@saout.de

On 11/03/2011 04:32 PM, Sebastian Steinhuber wrote:
> It seems that the patch was committed to 2.6.32 and 2.6.33 for now,
> according to LKML.
> However, I reproduced the behavior with chromium and google-chrome.
> Maybe the patch was not commited to mainline:

It is in mainline and it is in queue for 3.0.9 and 3.1.1 now.

Milan