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 yLX6OuYSy8hf for ; Tue, 16 Aug 2011 23:55:15 +0200 (CEST) Received: from archlinux.org (gerolde.archlinux.org [66.211.214.132]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 16 Aug 2011 23:55:15 +0200 (CEST) Message-ID: <4E4AE740.9020800@archlinux.org> Date: Tue, 16 Aug 2011 23:55:12 +0200 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= MIME-Version: 1.0 References: <4E4AD6F2.8020800@archlinux.org> <4E4AE4DB.30205@redhat.com> In-Reply-To: <4E4AE4DB.30205@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigF5C13D76487DE71B97B49D60" 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: Milan Broz Cc: dm-crypt This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF5C13D76487DE71B97B49D60 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 16.08.2011 23:44, schrieb Milan Broz: > On 08/16/2011 10:45 PM, Thomas B=E4chler wrote: >> I am getting reports of this error again: >> >> semid 491524: semop failed for cookie 0xd4dc159: incorrect semaphore s= tate >> Failed to set a proper state for notification semaphore identified by >> cookie value 223199577 (0xd4dc159) to initialize waiting for incoming >> notifications. >> >> This issue is so weird that I don't know where to start. Apparently, >> this problem appears whenever chromium is running, and disappears when= >> you quit chromium. I'm confused about this. Very confused. >=20 > I know that this bug is still there. I think that the problem is: >=20 > - kernel, in response to devmapper library request, send uevent with co= okie > - kernel reports failure (despite uevent was sent), I guess it is > some memory allocation error later > - libdevmapper takes error path, destroying semaphore, which was alread= y > destroyed in udev rules >=20 > So my guess is that connection with chromium just it perhaps allocates = most > of system memory and some allocation in kernel perhaps fail then. Then this would probably be reproducible with other programs, too. So far, the connection has been only made with chromium. I would love to find another test case though. > The final state should be correct, so you can (I hope) ignore that erro= r > for now. Don't the LUKS commands abort after this error? (Don't remember). > It is not a cryptsetup bug but I would like to fix it anyway, > the problem is the bug appears and disappears quite randomly. >=20 > Does anyone see this bug in some other libdevmapper user? > (lvm, multipath, kpartx, ... ?) I have only seen this with cryptsetup so far. > (Another possibility is that you have broken udev rules and > "dmsetup udevcomplete" is called twice there, but I do not think it > the issue.) Udev rules are all taken directly from upstream udev and device-mapper. --------------enigF5C13D76487DE71B97B49D60 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAk5K50AACgkQEda5KzHP/VDPeQCgvI6ag781pAEmA4hocNrQWgLw 7ZgAn19FZUQhbqkMQU7K/xmqxn6yEPz+ =jSWM -----END PGP SIGNATURE----- --------------enigF5C13D76487DE71B97B49D60--