linux-kernel - Re: Kernel crash on 2.6.31.x (kcryptd: page allocation failure..)

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: <200910190141.50752.elendil@planet.nl>
Date:	Mon, 19 Oct 2009 01:41:49 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Sven Geggus <lists@...hsschwanzdomain.de>
Cc:	linux-kernel@...r.kernel.org, Mel Gorman <mel@....ul.ie>,
	linux-mm@...ck.org,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: Kernel crash on 2.6.31.x (kcryptd: page allocation failure..)

(Sven: For kernel mailing lists please always do a "reply to all".
Although some other communities do not want that, it is standard for the 
kernel community. It is needed because otherwise, with the huge amount of 
traffic on the linux-kernel list, people are too likely to miss replies.)

Sven Geggus wrote:
> Frans Pop <elendil@...net.nl> wrote:
> 
>> What is the _exact_ command sequence you use to reproduce it? I already
>> have a testcase, but a second test case, or a simpler one, may be
>> useful. 
> 
> Not a particular easy testcase. This is what I did:
> 
> On the crashing machine with the dm-encrypted xfs volume:
> ionice -c 3 socat TCP4-LISTEN:5555 - >backup.tar
> 
> On the source machine:
> tar cv dir |socat - TCP4:targetmachine:5555
> 
> You will certainly not need to use tar.
> 
> socat /dev/zero TCP4:targetmachine:5555 should work as well.
> 
> I don't know if TCP traffic is really needed probably it is.

Thanks.

In the mean time I've been able to trace the culprit. Could you please try 
if reverting 373c0a7e + 8aa7e847 [1] on top of 2.6.31 fixes the issue for 
you?

Cheers,
FJP

[1] The first commit is a build fix for the second.
--
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/