All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt <dm-crypt@saout.de>, Peter Rajnoha <prajnoha@redhat.com>,
	arne waldgruber <wurstsalat@gmail.com>
Subject: Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"
Date: Fri, 28 Jan 2011 09:23:49 +0100	[thread overview]
Message-ID: <4D427D15.4030704@archlinux.org> (raw)
In-Reply-To: <4D41E6B5.7000100@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

Am 27.01.2011 22:42, schrieb Milan Broz:
> 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.

Right now, I am forwarding messages between this list and the bug report
here: https://bugs.archlinux.org/task/22351

I cannot reproduce the problem myself.

> Also please paste debug log from old (working) version to that bug so we
> can check if anything changed.

I asked for that info. I also added the original reporter as a CC, maybe
that will speed things up.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2011-01-28  8:23 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
2011-01-28  8:23       ` Thomas Bächler [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=4D427D15.4030704@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=dm-crypt@saout.de \
    --cc=mbroz@redhat.com \
    --cc=prajnoha@redhat.com \
    --cc=wurstsalat@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.