Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 9 Oct 2009 14:04:03 +0200 (CEST) Received: from liesel.fritha.org (localhost [127.0.0.1]) by liesel.fritha.org (Postfix) with ESMTP id 59096197CE9E for ; Fri, 9 Oct 2009 14:04:01 +0200 (CEST) Date: Fri, 09 Oct 2009 14:04:01 +0200 Message-ID: <87pr8wlqoe.wl%htd@fancy-poultry.org> From: Heinz Diehl In-Reply-To: <4ACF14CE.1060802@redhat.com> References: <20091009074743.GA7885@fancy-poultry.org> <4ACF14CE.1060802@redhat.com> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: Re: [dm-crypt] RC1/2 misbehaviour (bug?) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de At Fri, 09 Oct 2009 12:47:42 +0200, Milan Broz wrote: > Run cryptsetup with --debug and also check syslog and you will see that it retries > the remove. Did it, you're right. > You will probably find error that temporary-cryptsetup-$PID device is open and cannot > be removed. Please report it to your distro as bug, you will need check who opened > this device (I guess it is blkid from some generic udev rule) Yes, I've seen this too. I'm on opensuse 11.1. > Maybe I should add some message to debug about proces name opening that internal device... That would be helpful, thanks! > Note that it is possible security problem - keystore device contains hashed master > key, no other process except cryptsetup should read that (and store anywhere in > unlocked memory). This is ugly as hell. I will report this to the opensuse people and try to fix this immediately on my system. Thanks, Heinz.