From: Milan Broz <mbroz@redhat.com>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: dm-crypt <dm-crypt@saout.de>, Peter Rajnoha <prajnoha@redhat.com>
Subject: Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"
Date: Thu, 27 Jan 2011 22:42:13 +0100 [thread overview]
Message-ID: <4D41E6B5.7000100@redhat.com> (raw)
In-Reply-To: <4D41A3BB.5080407@archlinux.org>
On 01/27/2011 05:56 PM, Thomas Bächler wrote:
> Am 25.01.2011 00:16, schrieb Milan Broz:
> The reportee has installed device-mapper 2.02.81. The problem occurs
> only with cryptsetup 1.2.0, not 1.1.3.
strange, there should not be any change in cryptsetup related to this.
If you have some reproducer for it, please let me know.
Also please paste debug log from old (working) version to that bug so we
can check if anything changed.
Thanks,
Milan
next prev parent reply other threads:[~2011-01-27 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 22:55 [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state" Thomas Bächler
2011-01-24 23:16 ` Milan Broz
2011-01-27 16:56 ` Thomas Bächler
2011-01-27 21:42 ` Milan Broz [this message]
2011-01-28 8:23 ` Thomas Bächler
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=4D41E6B5.7000100@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=prajnoha@redhat.com \
--cc=thomas@archlinux.org \
/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