DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: shyam prasad <shyam_12i@yahoo.co.uk>,
	"dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] cryptsetup remove
Date: Sat, 02 Nov 2013 09:45:05 +0100	[thread overview]
Message-ID: <5274BB91.4030309@gmail.com> (raw)
In-Reply-To: <1383160837.32475.YahooMailNeo@web171201.mail.ir2.yahoo.com>

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

      reply	other threads:[~2013-11-02  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 19:20 [dm-crypt] cryptsetup remove shyam prasad
2013-11-02  8:45 ` Milan Broz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5274BB91.4030309@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=shyam_12i@yahoo.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox