linux-kernel - Re: cryptsetup + lvm on usb disk, unusable /dev/dm-* after suspend/resume cycle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100726155627.GN31966@localhost>
Date:	Mon, 26 Jul 2010 17:56:27 +0200
From:	Nils Radtke <Nils.Radtke@...nk-Future.de>
To:	Milan Broz <mbroz@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: cryptsetup + lvm on usb disk, unusable /dev/dm-* after
 suspend/resume   cycle

  Hi Milan,

  Thank you for your explanation.

  So I'll try to find logs regarding this issue (won't be easy though..).

  On the other hand, the usb device survives suspend/resume normally, that is,
  when using a plain disk, std partition etc.

  Ok, I'm going for the logs and if found be back.

  Thank you again for your help.

                  Nils

On Mon 2010-07-26 @ 03-22-45PM +0200, Milan Broz wrote: 
# On 07/26/2010 03:06 PM, Nils Radtke wrote:
# > That's what I tried and failed gloriously. I'm trying to revive my memory about the 
# > situation: fs could be unmounted, however, the cryptsetup luksClose failed (IRC) and 
# > therefore the dmsetup remove consequently failed also.
# 
# So instead of "cryptsetup luksClose" use dmsetup remove for crypt device too
# (There was a bug in some version of cryptsetup which failed close if underlying device
# disappeared, should be fixed in >=1.1.2, anyway "dmsetup remove" is low-level equivalent.)
# 
# Also see man page and "dmsetup remove -f" flag.
# 
# The usb device reinitialization is separate problem, maybe someone can help if you provide
# more logs.
# 
# Milan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/