linux-kernel - Re: [dm-crypt] INFO: task mount:11202 blocked for more than 120 seconds

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080318005653.GA14575@gondor.apana.org.au>
Date:	Tue, 18 Mar 2008 08:56:53 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Christian Kujau <lists@...dbynature.de>, Chr <chunkeey@....de>,
	Milan Broz <mbroz@...hat.com>, David Chinner <dgc@....com>,
	LKML <linux-kernel@...r.kernel.org>, xfs@....sgi.com,
	dm-devel@...hat.com, dm-crypt@...ut.de,
	Ritesh Raj Sarraf <rrs@...earchut.com>
Subject: Re: [dm-crypt] INFO: task mount:11202 blocked for more than 120 seconds

On Mon, Mar 17, 2008 at 05:36:09PM +0000, Alasdair G Kergon wrote:
> Latest version for everyone to try:
> 
> From: Milan Broz <mbroz@...hat.com>
> 
> Fix regression in dm-crypt introduced in commit
> 3a7f6c990ad04e6f576a159876c602d14d6f7fef
> (dm crypt: use async crypto).
> 
> If write requests need to be split into pieces, the code must not
> process them in parallel because the crypto context cannot be shared.
> So there can be parallel crypto operations on one part of the write,
> but only one write bio can be processed at a time.

Could you explain this part please? Crypto tfm objects are meant
to be reentrant, synchronous or not.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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/