From: Chr <chunkeey@web.de>
To: Milan Broz <mbroz@redhat.com>
Subject: [dm-crypt] INFO: task mount:11202 blocked for more than 120 seconds
Date: Sat, 15 Mar 2008 14:32:10 +0100
User-Agent: KMail/1.9.9
Cc: David Chinner <dgc@sgi.com>, Christian Kujau <lists@nerdbynature.de>,
       LKML <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com,
       dm-devel@redhat.com, Alasdair G Kergon <agk@redhat.com>,
       dm-crypt@saout.de
References: <alpine.DEB.1.00.0803072116420.7723@sheep.housecafe.de> <47DA44EB.8000307@redhat.com> <200803150108.04008.chunkeey@web.de>
In-Reply-To: <200803150108.04008.chunkeey@web.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200803151432.11125.chunkeey@web.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 921
Lines: 30

>On Sat, Mar 15, 2008 at 01:21:04AM +0100, Ulrich Lukas wrote:
>> With that patch applied, writing seems to work again.
>?
> Current version of the patch is below. ?It's still not quite finished.
>
:-/, both patches freezes here... 

I'll try to revert:

commit  3a7f6c990ad04e6f576a159876c602d14d6f7fef
dm crypt: use async crypto

dm-crypt: Use crypto ablkcipher interface
Move encrypt/decrypt core to async crypto call.

maybe it isn't the async stuff after all..

>> Btw, is this a regression because of the changed 2.6.25(-rc) code or is
>> it just a coincidence that it worked before?
>
>Introduced during code changes to support async crypto interface.

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