From: Herbert Xu Subject: Re: Re: next-20081125: crypto hard disk gets unaccessable Date: Mon, 1 Dec 2008 12:57:49 +0800 Message-ID: <20081201045749.GA18292@gondor.apana.org.au> References: <20081128063355.GA4700@denkbrett.schottelius.org> <20081129192939.925275f0.akpm@linux-foundation.org> <49332CC6.4080606@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christophe Saout , Nico -telmich- Schottelius , LKML , device-mapper development , linux-next@vger.kernel.org, linux-crypto@vger.kernel.org, Herbert@redhat.com To: Milan Broz Return-path: Content-Disposition: inline In-Reply-To: <49332CC6.4080606@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com List-Id: linux-crypto.vger.kernel.org On Mon, Dec 01, 2008 at 01:16:06AM +0100, Milan Broz wrote: > > > [69186.618468] [] ? crypto_cbc_encrypt+0xfa/0x15a [cbc] > > [69186.618481] [] ? aes_encrypt+0x0/0x7 [aes_x86_64] > > [69186.618494] [] ? async_encrypt+0x35/0x3a [crypto_blkcipher] > > [69186.618509] [] ? crypt_convert+0x1d2/0x253 [dm_crypt] > > [69186.618522] [] ? kcryptd_crypt+0x3e6/0x407 [dm_crypt] > > [69186.618533] [] ? kcryptd_crypt+0x0/0x407 [dm_crypt] > > I assume that crypto run here synchronously (not through asynchronous completion callback). > > Herbert - is my guess ok? (The asynchronous handling in dm-crypt was the only part changed recently.) > (And I think that except crypto hw nobody uses asynchronous mode yet by default.) Yes that's definitely synchronous. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt