linux-kernel - Fwd: [dm-crypt] [BUG] bad performance and system stalls when using dm-crypt

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikqhMbW7sWbbU_we5YE9Y9U=MPUTm553AmCyH51@mail.gmail.com>
Date:	Mon, 25 Oct 2010 02:32:52 +1100
From:	dave b <db.pub.mail@...il.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Fwd: [dm-crypt] [BUG] bad performance and system stalls when using dm-crypt

I am forwarding this to the linux kernel mailing list to see if anyone
is actually interested with this bug or not. I suspect that the patch
to allow DM-CRYPT to use multiple cpus(Scale to multiple CPUs) will
remove most of the problem but *not* all of it. As I previously was
triggering the bug on a single core system.

See https://bugzilla.kernel.org/show_bug.cgi?id=18302 for the original thread.
I filed this as bug  18302 at
https://bugzilla.kernel.org/show_bug.cgi?id=18302 .

---------- Forwarded message ----------
From: dave b <db.pub.mail@...il.com>
Date: 7 October 2010 04:58
Subject: Re: [dm-crypt] [BUG] bad performance and system stalls when
using dm-crypt
To: Milan Broz <mbroz@...hat.com>
Cc: dm-crypt@...ut.de

On 12 September 2010 21:45, dave b <db.pub.mail@...il.com> wrote:
> On 12 September 2010 19:07, Milan Broz <mbroz@...hat.com> wrote:
>> On 09/12/2010 10:36 AM, dave b wrote:
>>>
>>> Should I forward my 'bug' to the linux kernel maliing list ?
>>
>> Better report it to kernel bugzilla, it is better for tracking.
>> (Also see https://bugzilla.kernel.org/show_bug.cgi?id=17892 )
>
> Will do :)
>

Ok no one has responded to that bug ... :/
On a system lock up I ssh into the box and saw wait time was 83% in top.
I also saw that kcrypd was using 23% of cpu time - and that only one
core was in use.
1012 root      20   0     0    0    0 S   11  0.0  30:15.46 kcryptd

The system was stalled for 20minutes ...

load average: 19.16, 15.74, 11.43

--
Let me take you a button-hole lower.            -- William Shakespeare, "Love's
Labour's Lost"
--
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/