From: Milan Broz <mbroz@redhat.com>
To: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>
Cc: Christophe Saout <christophe@saout.de>,
LKML <linux-kernel@vger.kernel.org>,
device-mapper development <dm-devel@redhat.com>,
linux-next@vger.kernel.org, linux-crypto@vger.kernel.org,
Herbert@redhat.com, Xu <herbert@gondor.apana.org.au>
Subject: Re: Re: next-20081125: crypto hard disk gets unaccessable
Date: Mon, 01 Dec 2008 01:16:06 +0100 [thread overview]
Message-ID: <49332CC6.4080606@redhat.com> (raw)
In-Reply-To: <20081129192939.925275f0.akpm@linux-foundation.org>
Andrew Morton wrote:
> (cc's added)
>
>> After about four suspend & resume operations in the midst of editing
>> a file, the system beeped twice and issued this error:
Did this work before? If so, please can you provide version where
it works?
It is suspend to encrypted swap?
There should not be any recent change in dm-crypt related to this path,
so I expect it is some bug related to suspend/resume in combination with
running crypto - like corruption of some memory caused during suspend...
> [lots of snippage]
>> [69186.618357] RIP: 0010:[<ffffffff8031f246>] [<ffffffff8031f246>] crypto_xor+0x7/0x48
> [69186.618468] [<ffffffffa027226a>] ? crypto_cbc_encrypt+0xfa/0x15a [cbc]
> [69186.618481] [<ffffffffa0285705>] ? aes_encrypt+0x0/0x7 [aes_x86_64]
> [69186.618494] [<ffffffffa020667d>] ? async_encrypt+0x35/0x3a [crypto_blkcipher]
> [69186.618509] [<ffffffffa0269a6f>] ? crypt_convert+0x1d2/0x253 [dm_crypt]
> [69186.618522] [<ffffffffa0269ed6>] ? kcryptd_crypt+0x3e6/0x407 [dm_crypt]
> [69186.618533] [<ffffffffa0269af0>] ? 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.)
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2008-12-01 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 6:33 next-20081125: crypto hard disk gets unaccessable Nico -telmich- Schottelius
2008-11-30 3:29 ` Andrew Morton
2008-11-30 4:32 ` Herbert Xu
2008-12-01 0:16 ` Milan Broz [this message]
2008-12-01 4:57 ` Herbert Xu
2008-12-01 17:36 ` [dm-devel] " Nico -telmich- Schottelius
2008-12-01 17:35 ` Nico -telmich- Schottelius
2008-12-02 11:55 ` Nico -telmich- Schottelius
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=49332CC6.4080606@redhat.com \
--to=mbroz@redhat.com \
--cc=Herbert@redhat.com \
--cc=christophe@saout.de \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nico-linux-next@schottelius.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).