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 IcLW2fhkbzaT for ; Wed, 30 Oct 2013 20:20:39 +0100 (CET) Received: from nm29-vm7.bullet.mail.ir2.yahoo.com (nm29-vm7.bullet.mail.ir2.yahoo.com [212.82.97.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 30 Oct 2013 20:20:38 +0100 (CET) Message-ID: <1383160837.32475.YahooMailNeo@web171201.mail.ir2.yahoo.com> Date: Wed, 30 Oct 2013 19:20:37 +0000 (GMT) From: shyam prasad MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1358838705-1624048488-1383160837=:32475" Subject: [dm-crypt] cryptsetup remove Reply-To: shyam prasad List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "dm-crypt@saout.de" --1358838705-1624048488-1383160837=:32475 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello,=0A=0AI am using cryptsetup-1.2 without luks and I have noticed that = while removing the mapped device using 'cryptsetup remove', cryptsetup does= a read operation. I have found that this is not true in cryptsetup-1.5.1. = Is this a side effect of a change or was this explicitly modified. If it wa= s intentional, could someone point me to the patch.=0A=0A=0AThanks=0A --1358838705-1624048488-1383160837=:32475 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hello,

I am using cryptsetup-1.2 without luks and I have noticed t= hat while removing the mapped device using 'cryptsetup remove', cryptsetup = does a read operation. I have found that this is not true in cryptsetup-1.5= .1. Is this a side effect of a change or was this explicitly modified. If i= t was intentional, could someone point me to the patch.

<= /div>

Thanks

--1358838705-1624048488-1383160837=:32475-- 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 mxNhfVHqa7Mt for ; Sat, 2 Nov 2013 10:15:49 +0100 (CET) Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 2 Nov 2013 10:15:49 +0100 (CET) Received: by mail-ea0-f171.google.com with SMTP id h10so2454755eak.2 for ; Sat, 02 Nov 2013 02:15:48 -0700 (PDT) Message-ID: <5274BB91.4030309@gmail.com> Date: Sat, 02 Nov 2013 09:45:05 +0100 From: Milan Broz MIME-Version: 1.0 References: <1383160837.32475.YahooMailNeo@web171201.mail.ir2.yahoo.com> In-Reply-To: <1383160837.32475.YahooMailNeo@web171201.mail.ir2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup remove List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: shyam prasad , "dm-crypt@saout.de" On 30.10.2013 20:20, shyam prasad wrote: > Hello, > > I am using cryptsetup-1.2 without luks and I have noticed that while > removing the mapped device using 'cryptsetup remove', cryptsetup does > a read operation. I have found that this is not true in > cryptsetup-1.5.1. Is this a side effect of a change or was this > explicitly modified. If it was intentional, could someone point me to > the patch. Can you be more specific? Which read operation, how did you see it - strace? And what's the real problem? I do not see any explicit read for removal of plain device. Note that a lot of scanning can happen through udev rules when some device is created, modified (it scans device after close for write) etc. Milan