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]

Date:	Wed, 26 Mar 2008 17:57:53 +0100
From:	Chr <chunkeey@....de>
To:	Alasdair G Kergon <agk@...hat.com>
Cc:	Christian Kujau <lists@...dbynature.de>,
	Milan Broz <mbroz@...hat.com>, David Chinner <dgc@....com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ritesh Raj Sarraf <rrs@...earchut.com>, dm-devel@...hat.com,
	dm-crypt@...ut.de, Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [dm-crypt] INFO: task mount:11202 blocked for more than 120 seconds

On Monday 17 March 2008 18:36:09 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.
>
> This is not optimal and the workqueue code need to be optimized for
> parallel processing, but for now it solves problem without affecting
> the performance of synchronous crypto operation (most of current
> dm-crypt users).
>
> Signed-off-by: Milan Broz <mbroz@...hat.com>
> Signed-off-by: Alasdair G Kergon <agk@...hat.com>
>
> [...]

Is there already a new, optimized version? Or is it postponed and someone will 
_hopefully_ merge  this patch into -rc7-gitX before we have a buggy mainline 
2.6.25?

Thanks,
	Chr  



--
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/