From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Tue, 20 Oct 2009 15:05:34 +0200 (CEST) MIME-version: 1.0 Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KRT00L0XDP97V00@mta-1.ms.rz.RWTH-Aachen.de> for dm-crypt@saout.de; Tue, 20 Oct 2009 15:05:33 +0200 (CEST) Received: from [134.61.47.76] ([unknown] [134.61.47.76]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KRT00BMVDP9W210@relay-auth-1.ms.rz.rwth-aachen.de> for dm-crypt@saout.de; Tue, 20 Oct 2009 15:05:33 +0200 (CEST) Message-id: <4ADDB59D.7050202@archlinux.org> Date: Tue, 20 Oct 2009 15:05:33 +0200 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= References: <4ADD7639.6060904@archlinux.org> <4ADD7B1F.9060704@redhat.com> <4ADD9876.8000006@redhat.com> <4ADDA96F.2080109@archlinux.org> <4ADDB2DE.9020401@redhat.com> In-reply-to: <4ADDB2DE.9020401@redhat.com> Content-type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary=------------enig47D68614F393784A4029148E Subject: Re: [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Rajnoha Cc: dm-crypt@saout.de, Milan Broz This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig47D68614F393784A4029148E Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Peter Rajnoha schrieb: > If I got him right, I think he meant direct listeners of the "KERNEL" u= dev > events like udevd does. Yes, we can't do much here - if anybody listens= to > the events this way, he is on his own (if we listen to UDEV udev events= , > then these ones will have those env vars set, so one can check them). Okay - which program would do that? > Yes, ignore_device is another way how to suppress the events somehow. B= ut > this one will ignore all the rules irrespective of the sequence when it= 's called. > When I tried this one first, I had a rule that sets the nodes and symli= nks > in /dev/mapper and just after that I called ignore_device, but it ignor= ed > everything. So this one can't be used either. Does it matter? If I remember correctly, libdevmapper creates the=20 /dev/mapper/* nodes itself even if udev isn't there. So cryptsetup would = create the temporary-cryptsetup-* node, access it and destroy it and=20 udev would ignore everything else - sounds like a good solution to me. I will deploy the rule mentioned in earlier posts as a workaroud for now = and then see what is happening upstream - once the upstream rules are in = a good state, I am more than willing to use those rather than=20 distro-specific ones. --------------enig47D68614F393784A4029148E 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkrdtZ0ACgkQEda5KzHP/VDNRgCeKa5GUhzMy+yPTDVGJJhjYCBG XNAAnAp/l6qX5T//0DUGgYa+iliJaad8 =eokf -----END PGP SIGNATURE----- --------------enig47D68614F393784A4029148E--